uEFI Firmware Update

Installation README File

Version: 3.20 BUILDID: D7E174B

(C) Copyright International Business Machines Corporation 2011 - 2018.

All rights reserved.
US Government Users Restricted Rights - Use, duplication, or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.

CONTENTS
________

1.0 Overview
2.0 Installation and Setup Instructions
3.0 Configuration Information
4.0 Unattended Mode
5.0 Web Sites and Support Phone Number
6.0 Trademarks and Notices
7.0 Disclaimer

1.0 Overview

1.1 This README file contains the latest information about

installing the uEFI firmware update.

- Acronyms:
AMM - Advanced Management Module
CMM - Chassis Management Module
IMM2 - Integrated Management Module

1.2 Please refer to following link for most updated Operating Systems
support list.
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/

1.3 Limitations:

- This flash utility is only able to update systems in which the

IMM2 can be reached via an ethernet connection. If the IMM2 cannot be
reached due to lack of a connection or firewall protections, then
the update will fail.

1.4 Enhancements:

- Refer to the change history file ibm_fw_uefi_d7e174b-3.20_anyos_32-

64.chg
for a history of enhancements and fixes.

1.5 Recommendations and Prerequisites for the Update:

- IMPORTANT: Make sure the current IMM2 firmware level is 1.50 or later
before you update the uEFI firmware or DSA Preboot firmware.
The recommended firmware update sequence is IMM2 followed by uEFI
followed by DSA Preboot.

- IMPORTANT: When updating via any method other than UpdateXpress

 Systems Packs, Bootable Media Creator, CMM, or AMM, wait at least
six minutes after the IMM2 update completes before you initiate any
planned uEFI or DSA Preboot firmware updates.

- IMPORTANT: When updating through CMM or AMM , after the IMM2 update is
complete, wait at least fifteen minutes before you initiate any
planned uEFI or DSA Preboot firmware updates.

- Note: Updated firmware version numbers might not be visible in SMBIOS

Tables until after the server is rebooted.

- In Windows Server 2008, the firewall may be enabled by default.

In some configurations, this could prevent the flash utility from
succeeding. The firewall may need to be disabled if it is suspected
to be preventing the update traffic.

- Updating the uEFI firmware using the IMM2 ethernet over USB interface
requires operating system drivers and configuration for the USB
interface.

- In order to install the device driver for LAN-over-USB device on

Windows,
there must be no network device on the system configured with an IP
address of 169.254.x.y other than the IBM USB Remote NDIS Network
Device (the LAN-over-USB device).

- In order to load the device driver for LAN-over-USB device on Linux,

there
must be no network device on the system configured with an IP
address of 169.254.x.y other than the CDC Ethernet Device (the
LAN-over-USB device).

- The update package will attempt to perform the setup if needed. If

the automatic setup fails or it is desired to setup the USB LAN via
manual intervention, the following process can be used:

Windows Driver Installation

===========================
Perform the following steps to install ibm_rndis_server_os.inf:
These steps only need to be performed if the server is running
a Windows operating system and the ibm_rndis_server_os.inf
file has not been previously installed. The INF needs to be
installed only once. It is required by Windows operating systems
to detect and use the IMM2's Ethernet over USB functionality.

a). Extract the ibm_rndis_server_os.inf and device.cat files

from this update package and copy them to the
\WINDOWS\inf subdirectory.

b). For Windows Server 2003:

Install the INF by right-clicking on the file and selecting
Install. This generates a .PNF file of the same name in
\WINDOWS\inf.

For Windows Server 2008:

Go to Computer Management then Device Manager and find the RNDIS
Device.
Select properties -> Driver -> Reinstall driver
 Point the system to the \Windows\inf folder where it will find
the .inf file and install the device.

For Windows Server 2012:

Go to Computer Management then Device Manager and find the RNDIS
Device.
Select properties -> Driver -> Update driver
Point the system to the \Windows\inf folder where it will find
the .inf file and install the device.

c). Go to Computer Management then Device Manager and right-click

on "Network adapters" and select "Scan for hardware changes".
You should see a small popup that says "Found New Hardware"
and "Ethernet Device".

d). The New Hardware Wizard should start automatically. When it asks
"Can Windows connect to Windows Update to search for software?"
select "No, not this time". Then click Next to continue.

e). When it asks "What do you want the wizard to do?" select
"Install from a list or specific location (Advanced)". Then
click Next to continue.

f). When "Please choose your search and installation options" is

displayed, select "Don't search. I will choose the driver to
install." Then click Next to continue.

g). When "Select a hardware type, and then click Next." is

displayed, select "Network adapters". Then click Next to
continue.

h). When the dialog comes up, displaying "Completing the Found New
Hardware Wizard". Click Finish.

i). A new Local Area Connection should come up. (for example Local
Area Connection 4) and may state "This connection has limited or
no connectivity." You can ignore this message.

j). Go back to the Device Manager. "IBM USB Remote NDIS Network
Device" should now show up under "Network Adapters".

k). Open a command prompt and type "ipconfig". You should see the
"Local Area Connection" for the IBM USB RNDIS and it should have
an IP address in the range 169.254.xxx.xxx.

l). Go to Start -> Control Panel -> Network Connections. Right

click on the device named "IBM USB RNDIS Network Device"
and select "properties".

m). In the scroll down box, select "Internet Protocol(TCP/IP)"

and click on the properties button.

n). Select the radio button labeled "Use the following IP address".
In the IP address field put an address in the range
169.254.95.xxx with a Subnet mask of 255.255.0.0.
The recommended value for this step is 169.254.95.119.

o). Click the advanced button in the lower corner of the window.
Under the "IP Settings" tab click the "Add..." tab in the
 "IP addresses" frame.

p). In the IP address field, put an address in the range

169.254.95.xxx with a subnet mask of 255.255.255.0.
The recommended value for this step is 169.254.95.120.

q). Click the add button, the OK button for the

"Advanced TCP/IP Settings" window, and the OK button for the
"Internet Protocol(TCP/IP) Properties" window. Then click
close on "Wireless Network Connection Properties".

Linux Driver Requirements

==========================
The IMM2 Ethernet over USB interface requires the usbnet and
cdc_ether drivers to be loaded. If the drivers have not been
installed, use modprobe to install them. When these drivers are
loaded, the IMM2's USB network interface will show up as a network
device in the operating system.

If the drivers have not been installed (such as the case with
RHEL4), use "modprobe" to install them. To do this, open terminal
and type:
modprobe usbnet

To discover the name that the operating system has assigned to the
IMM2's USB network interface, type
dmesg | grep -i cdc_ether

The interface should be configured with ifconfig to have an IP

address in the range 169.254.xxx.xxx. For example:
ifconfig IMM_device_name 169.254.1.102 netmask 255.255.0.0

Updating via IMM2

=================
If you are updating the uEFI firmware through the IMM2
user interfaces, you should make sure that the server is powered up
and booted into the Operating System, otherwise the IMM2 is unable to
access the uEFI flash device.

1.6 Dependencies:

1.6.1 Windows Server 2003 R2 based operating systems

The Microsoft IPMI device driver is not installed by default

with Microsoft Windows Server 2003 R2 based operating systems.

To install the Microsoft IPMI device driver, complete the

following:

1. Click Start -> Control Panel -> Add/Remove Programs.

2. Click Add/Remove Windows Components.
3. From the component list, select Management and Monitoring
Tools, and then click Details.
4. Select Hardware Management.
5. Click Next. The installation wizard opens and guides you
through the installation. The Windows installation disk may
 be required.

2.0 Installation and Setup Instructions

2.1 If you are updating UEFI or IMM2 using VMware, the following
steps should be completed prior to the update to ensure
that the flash utility can connect to the IMM2.

VMware 3.5
==========
1. esxcfg-firewall --allowOutgoing
2. ifconfig cdceth0 169.254.x.x
3. route del -net 169.254.0.0 netmask 255.255.0.0 lo
4. Then ping 169.254.95.118 to make sure that you can connect
to the IMM2 using the Ethernet over USB interface

VMware 4.0/4.1
==============
1. esxcfg-firewall --allowOutgoing
2. esxcfg-vswitch -l
3. esxcfg-vswitch -L vusb0 vSwitch0
4. ifconfig vswif0 169.254.xxx.xxx netmask 255.255.0.0
5. Then ping 169.254.95.118 to make sure that you can connect
to the IMM2 using the Ethernet over USB interface

VMware 5.0/5.1
==========
1. esxcli network firewall set -d true
2. esxcfg-vswitch -l
3. esxcfg-vswitch -L vusb0 vSwitch0
4. ifconfig vswif0 169.254.xxx.xxx netmask 255.255.0.0
5. Then ping 169.254.95.118 to make sure that you can connect
to the IMM2 using the Ethernet over USB interface

The procedures to update the uEFI are as follows:

Note: In Windows Server 2008, the firewall may be enabled by default.

In some configurations, this could prevent the flash utility from
succeeding. The firewall may need to be disabled if it is suspected
to be preventing the update traffic.

2.2 Using the command line interface

- Download UpdateXpress System Packs Installer (UXSPI) from IBM website:

http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-
XPRESS

- Place all update files [UXSPI, xml and uxz file] into the same
directory on your client system [windows].

- Open a CMD prompt.

- Ensure you are able to ping OS remotely from your client.

- If remote:
Run the uEFI Update with the following command line:
"uxspi.exe update -s all --latest --remote=<HOST IP> --remote-user=<HOST
USERID> --remote-password=<HOST PASSWORD>"
 - If local:
"uxspi update -l <file>.xml -s all"

NOTE: The version of uxspi is updated periodically. The uxspi.exe

may have a version associated with the name (ie uxspi920.exe)

- Ensure the connection to the remote server is made successfully,

able to copy the required files to the remote server, and run
the UEFI update successfully on the Windows Server.

- If you want to deploy the appropriate set of updates to the target

system even if the system version is newer than the update package
version, use "-s" to specify the update id you want to downgrade
or use "-s all".

3.0 Configuration Information

- This update package does not provide the ability to set or modify
uEFI configuration settings.

4.0 Unattended Mode

4.1 Performing the update in unattended mode

- Place all update files [UXSPI, xml and uxz file] into the same
directory.

- If remote:
Run the uEFI Update with the following command line:
"uxspi.exe update -s all --latest --remote=<HOST IP> --remote-user=<HOST
USERID> --remote-password=<HOST PASSWORD>"

- If local:
"uxspi update -l <file>.xml -u -s all"

NOTE: The version of uxspi is updated periodically. The uxspi.exe

may have a version associated with the name (ie uxspi920.exe)

5.0 Web Sites and Support Phone Number

5.1 IBM Support Web Site:

http://www.ibm.com/systems/support

5.2 IBM Marketing Web Site:

http://www-03.ibm.com/systems/x/

5.3 If you have any questions about this update, or problems

applying the update go to the following Help Center World
Telephone Numbers URL:
http://www.ibm.com/planetwide/index.html

6.0 Trademarks and Notices

6.1 IBM and the e(logo) are registered trademarks of

International Business Machines Corporation in the United.
 States, other countries, or both.

6.2 U.S. Government Users Restricted Rights - Use, duplication

or disclosure restricted by GSA ADP Contract with IBM
Corporation. IBM web site pages may contain other
proprietary notices and copyright information which should
be observed.

Microsoft and Windows are registered trademarks of Microsoft

Corporation in the United States, other countries, or both.

Other company, product, or service names may be trademarks

or service marks of others.

7.0 Disclaimer

THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY

KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR
IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES
OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH
RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING
THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR
COPYRIGHTS.