================================================================================
Release Notes for
NEC Express5800/R320c,R310c
BMC Firmware Revision 03.26
================================================================================
Software name     : NEC Express5800/R320c,R310c BMC Firmware update module
Module file       : 010008-G02_636059187954668636.zip
Models            : NEC Express5800/R320c-M4 (N8800-174F/174E, NP8800-174FP1)
                    NEC Express5800/R320c-E4 (N8800-173F/173E, NP8800-173FP1)
                    NEC Express5800/R310c-E4 (N8800-178F)
Operating System  : This software supports the following OS
                    - Microsoft(R) Windows Server(R) 2008 R2
                    - Microsoft(R) Windows Server(R) 2012 Standard
                    - Microsoft(R) Windows Server(R) 2012 Datacenter
                    - Red Hat Enterprise Linux(R) 6.5
                    - VMware ESXi(R) 5.1
Target users      : See [Server models for update] below
Type              : BMC Firmware
================================================================================

--------------------------------------------------------------------------------
[About the software]

This BMC Firmware update module (hereinafter called "this software") supports 
the following functional enhancement in the NEC Express5800/R320c-M4, R320c-E4
and NEC Express5800/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.

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

--------------------------------------------------------------------------------
[User License Agreement]

NEC Corporation ("NEC") grants you the right to use the software program
("Software") under the terms and conditions of this Agreement only in the 
country in which you acquired the Software. You shall agree to all provisions 
of this Agreement and assume responsibility for selection, installation, use 
and effect of the Software purchased for your desired effect.

1. Terms 
1.1 This Agreement shall come into force on the date of your receipt of the
    Software.
1.2 You may terminate the license granted hereunder by notifying us in writing
    at least one month prior to the desired termination date.
1.3 NEC may terminate the license granted you hereunder at any time if you
    fail to comply with any terms and conditions of this Agreement. 
1.4 The license to the Software shall remain in force until the license is
    terminated on the date set forth hereunder. 
1.5 Upon termination of the license, other rights granted you hereunder shall
    also be terminated. You must destroy or dispose of the Software, any copies
    of the Software and manual and other materials provided with the Software. 

2. Copyright 
2.1 The Software shall solely be used in the NEC Express5800 servers and
    workstations.
2.2 NEC grants you the right to use the Software only in the country in which
    you acquired the Software in accordance with the conditions of the
    preceding paragraph.

3. Copying, altering, and combining of the Software
3.1 You may only make one copy of the Software solely for a backup purpose,
    provided, however, that the copy of the Software is loaded into permanent
    memory of the system. You may store the Software solely to prevent damages
    or loss of the memory media.
3.2 You shall place the copyright notice and other legends on each copy of the
    Software.
3.3 You may not use, copy, alter, combine, publish, reproduce the Software over
    the Internet, or otherwise dispose of the Software except as provided in
    this Agreement. 
3.4 You may not copy, publish the manual or other related documentation
    provided with the Software, or reproduce such manual and documentation over
    the Internet.
3.5 No intangible property right to the Software shall be transferred to you.

4. Transfer
4.1 You may assign your rights granted hereunder to a third party only if all
    conditions below are satisfied: 
    a. You shall assign and shall not retain this Agreement, the Software, all
       copies of the Software, or the manual or other related documentation
       provided with the Software. 
    b. The transferee agrees to this Agreement.
4.2 You shall not sublicense, assign, transfer, or otherwise dispose of the
    Software or the right of use to any third party except as provided herein.

5. Reverse compile
   You may not reverse engineer, decompile, or otherwise disassemble the
   Software.

6. Limitation of warranties
6.1 The Software is provided "as is" without warranty of any kind. In no event
    shall NEC be liable with respect to any claim by you on account of or
    arising out of the use of the Software.
6.2 Notwithstanding the provisions of the preceding paragraph, in case NEC
    makes any bug-fix version to the Software, NEC will, at its expense,
    furnish you with such bug-fix version, update version, or information in
    relation to such bug-fix or update version both in the source code form and
    object code form, and such bug-fix version or update version shall be
    considered as the licensed Software.

7. No liability 
    In no event shall NEC be liable for any indirect or consequential damages
     or loss of profit or damages based on any third party claim, even if NEC 
    has been advised of the possibility of such damages.

--------------------------------------------------------------------------------
[Update procedures]

  1. Download the module into any directory of hard disk.
  2. Extract the module into any directory.
  3. The software and its procedure manual will be extracted into the forder.

  You can refer to the procedure manual(ReadMe_E.txt) by Notepad of Windows(R) 
  OS. Execute the BMC firmware Update following the manual.

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

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

--------------------------------------------------------------------------------
Copyright NEC Corporation 2016