================================================================================
Release Notes for
NEC Express5800/R320d,R310d
BMC Firmware Revision 03.25
================================================================================
NEC Corporation.
March. 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/R320d-M4, R320d-E4 and R310d-E4 models:

BMC 03.25
  - For security measure, OpenSSL is renewed in 1.0.1m base.
  - TLS1.1/1.2 is 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.
  - 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.

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.

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

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

 - BMC Firmware versions to update:
    BMC Firmware Revision 03.15
    BMC Firmware Revision 03.18

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

 - 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 (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.25 Boot=00.09 Sdr=03.03
           ID 11/120 : Runtime=03.25 Boot=00.09 Sdr=03.03

         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.


 - <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-01215bmc_b00.09r03.25s03.03.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-01215bmc_b00.09r03.25s03.03.bin /tmp/fw

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

         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.25/00.09/03.03
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '03.25/00.09/03.03',
         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.25/00.09/03.03
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '03.25/00.09/03.03',
         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

November. 2016 BMC Firmware Revision: 03.18
  - The problem that a SSH connection to BMC and a connection to 
    EXPRESSSCOPEEngine3 can't sometimes is corrected.

March. 2016 BMC Firmware Revision: 03.25
  - For security measure, OpenSSL is renewed in 1.0.1m base.
  - TLS1.1/1.2 is 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.
  - 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.

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

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.
