================================================================================
Release Notes for
NEC Express5800/R320c,R310c
BMC Firmware Revision 03.26
================================================================================
NEC Corporation.
August. 2016

[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/R320c-M4, R320c-E4 and R310c-E4 models:

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

Note:
  - To prevent a system failure, please read this document carefully and 
    follow the procedure for successful update.  Should your system 
    malfunctions or is powered off due to an unplanned event during update (for
    example, power blackout or cutoff, lightening, and noise), the system may 
    be damaged and fails 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 is sometimes failed.

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

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

 - BMC Firmware versions to update:
    BMC Firmware Revision 02.15
    BMC Firmware Revision 03.07
    BMC Firmware Revision 03.15
    BMC Firmware Revision 03.25

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

NOTE:
When you apply to the following case, you do preceding work of the case, please.

  <CASE 1>
    If current BMC firmware version is 02.15, confirm the following.
    In case of
      - For 4 months or more months the system has been powered on
        ('Powered on' means both connect AC plugs.) or
      - You do not know how long has the system been powered on

  <CASE 2>
    If current BMC firmware version is 03.25 and less, confirm the following.
    In case of
      - You have performed ssh connection to BMC after system has been powered on
        ('Powered on' means both connect AC plugs.)

  When you apply to CASE 1 or CASE 2, you have to make the system shut down and 
  powered off for more than 30 seconds, powered on and after the system becomes 
  in Duplex state.
    ('Powered off' means both disconnect AC plugs.)
    ('Powered on' means both connect AC plugs.)
  Then you can start to update BMC Firmware.

  <CASE 3>
    If current BMC firmware version is 03.15 and less and the following problem 
    occurs.
    In case of
      - After setting the DNS address of the network setting item of BMC, the 
        problem of repeating a Primary change in a module occurs

  When you apply to CASE 3, please do the following one of workaround.
  Then you can start to update BMC Firmware.

  [Workaround 1]
    Please change the DNS address of the network setting item of both BMC to 
    "0.0.0.0".
    When doing this workaround, please return the DNS address to the beginning 
    after BMC update completion.

  [Workaround 2]
    When DNS server stops, while you update BMC Firmware, please operate DNS 
    server.

 - How to confirm 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>
        (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 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 BMC Firmware version (VMware ESXi(R)):

    (1) Login to 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, follows the below procedure.

   3-1. Preparation of Update

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

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

     (3) Terminate all the running application.

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

   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 because of an error if the screen appears soon.

     (2) Confirm the progress by 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>
            (Start->(down-arrow button)->NEC ESMPRO Agent->ft server utility)

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

         3. When update process is completed, Status shows 'Duplex, Duplex'.
            The update process will takes approximately 30 minutes.
            
     (3) Confirm whether update process is succeeded by ft server utility.

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

         Confirm firmware as follows.
           ID 10/120 : Runtime=03.26 Boot=00.09 Sdr=03.01
           ID 11/120 : Runtime=03.26 Boot=00.09 Sdr=03.01

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

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

     (5) After Firmware update completes, delete the unzip file 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 the system as a root user.

     (3) Terminate all the running application.

     (4) Download the zipped file into any directory of hard disk and 
         unzip the file into any directory. 
         Write down the path to the directory in which unzip the file.

         Only the following file is used by Firmware update.
         '062-01210bmc_b00.09r03.26s03.01.bin'

   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
         and PRIMARY LED unilluminated is 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 Step 3-1 
         in [Enter the file location of the new firmware] text box, and 
         select [Activate].

         <Input example>  '/tmp/062-01210bmc_b00.09r03.26s03.01.bin'

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

         When 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 displayed, select [ok].

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

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

         When 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 is succeeded by 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=03.26 Boot=00.09 Sdr=03.01

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

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

     (9) If the firmware update of secondary PCI module is completed, 
         Start the firmware update of another 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 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 start automatically.

         The update process will takes approximately 15 minutes.

    (13) Confirm whether update process is succeeded by 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=03.26 Boot=00.09 Sdr=03.01

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

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


 - <VMware ESXi(R)>:

   Follows the below procedure.

   3-1. Preparation of Update

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

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

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

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

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

         note) Only the following file is used by Firmware update.
               '062-01210bmc_b00.09r03.26s03.01.bin'

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

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

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

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

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

         4. BMC firmware file is copied to desired directory of 
            ftSys Management Appliance from CD/DVD.

            <Command example>
             # mkdir /tmp/fw
             # cp /mnt/cdrom/062-01210bmc_b00.09r03.26s03.01.bin /tmp/fw

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

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

                before: 062-01210bmc_b00.09r03.26s03.01.bin
                after : 062_01210bmc_b00_09r03_26s03_01.bin
                        '-'(hyphen) and '.'(period except the file extension),
                        change to '_'(underscore).

         5. After BMC firmware file is copied, unmount CD/DVD.

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

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

   3-2. Update procedure

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

         For <<bmc_file>>, specify the file path you have copied in Step 3-1.

     (2) The update process will take approximately 30 minutes.
         When the following messages are displayed, update completes.

         <Example>
          ----------------------------------------------
          Updated firmware on the device at path 11/120.
          Updated firmware on the device at path 10/120.
          ----------------------------------------------
            
     (3) Confirm whether update process is succeeded by following command.

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

         <Example>
          ----------------------------------------------
          Op State : DUPLEX
          :
          Firmware Rev : 03.26/00.09/03.01
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '03.26/00.09/03.01',
         Firmware update completes.

         Confirm whether another update process is succeeded 
         by following command.

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

         <Example>
          ----------------------------------------------
          Op State : DUPLEX
          :
          Firmware Rev : 03.26/00.09/03.01
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '03.26/00.09/03.01',
         Firmware update completes.

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

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

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

Jul. 2013 BMC Firmware Revision: 03.07
  - Fixes the malfanction that BMC reset occures when the system remains to be
    powered on for more than one half year. When the BMC reset occurs, 
    the IO module temporarily exits from the Duplex state and recovers to the 
    Duplex state automatically. However in rare cases, the system is booted 
    at this time.

Jul. 2014 BMC Firmware Revision: 03.15
  - Reduces the frequency writing to a flash memory.

March. 2016 BMC Firmware Revision: 03.25
  - For security measure, OpenSSL is renewed in 1.0.1m base.
  - EXPRESSSCOPEEngine3 is TLS1.1/1.2 supported.
  - The Self Signed SSL certificate which is being used for EXPRESSSCOPEEngine3
    is renewed in SHA-2.
  - It was confirmed that EXPRESSSCOPEEngine3 works in version 9/10/11
    of Internet Explorer(R).
  - The problem that remote KVM can't sometimes connect any more is corrected.
  - When the encryption of remote KVM is made effective by the environment of 
    Java7 and later, and it's connected to remote KVM, message of 
    "Connection Failure:Error in reading Video data!" is displayed.
    After that the problem that remote KVM can't connect any more is corrected.
  - After setting the DNS address of the network setting item of BMC, the IPMI
    command was an error, and it was corrected that the problem of repeating 
    a Primary change in a module sometimes occurs.
  - The problem that a SSH connection to BMC and a connection to 
    EXPRESSSCOPEEngine3 can't sometimes is corrected.

August. 2016 BMC Firmware Revision: 03.26
  - 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.

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