- UXSPI fails
to update xFW for one node of the IBM System x3950 X6
- Sometimes, UXSPI succeeds
in updating xFW for node0 of IBM System x3950 X6,
but fails to update xFW for node1.
Workaround
In this
case, you can follow these steps to recover the system.
- DC off the box.
- Remove the alternating current power source from both the top
and bottom nodes. Wait for all of the LEDs to turn off.
- Unplug all of the Compute books except slot 1.
- Connect the alternating current power source to only the bottom
node.
- Connect IMM enet to the bottom node.
- Log on to IMM web on the bottom node.
- Flash the IMM and uEFI code.
- DC on the box and let it get to uefi f1/setup screen.
- DC off the box.
- Unplug the bottom alternating current power source. Wait for all
of the LEDs to turn off.
- Unplug compute book in slot 1.
- Install compute book in slot 5.
- Connect the alternating current power source to the top node only.
- Install IMM enet to the top node.
- Log into IMM web on the top node.
- Load IMM and uEFI code.
- Connect the video to the top node.
- DC on the box.
- Boot to the uEFI setup screen.
- DC off the box.
- Remove the alternating current power source. Wait for all of the
LEDs to turn off.
- Install all of the compute books.
- Connect all of the alternating current power sources.
- Verify through the IMM, that the box has been setup as a two-node,
8-way box.
- DC on the box.
- Ensure that the box boots.
- Ensure that all of the code is up-to-date through the IMM web
interface on both nodes, or through uEFI setup.
- The error message: Exiting from the current instance is
displayed when only one instance of UXSPI is running.
- UXSPI uses
semaphores to prevent UXSPI from running
multiple instances at the same time. When UXSPI exits
ungracefully, the semaphore might not get released, preventing another
instance of UXSPI from
starting.
Workaround
Run UXSPI from the
command line using the -semdestroy option. Then,
run UXSPI as
usual.
- UXSPI does
not support running multiple copies of itself
- Because only
one UXSPI tool
should apply updates to a system at a time, UXSPI does not
support running multiple UXSPI tools
on a local system at the same time. You can, however, run the tools
against multiple remote systems by using the remote argument.
Workaround
To
use the
remote argument, you must set the environment
variable
UXSPI_MULTIPLE_INSTANCE to
1 on
the system running the tool. The following example demonstrates this
argument for Windows and simultaneously running remote updates on
servers 10.6.9.58 and 10.0 8.137:
SET UXSPI_MULTIPLE_INSTANCE=1
start cmd.exe /K uxspi500.exe up --remote=10.6.9.58
--remote-user=administrator --remote-password=passw0rd
start cmd.exe /K uxspi500.exe up --remote=10.0 8.137
--remote-user=administrator --remote-password=passw0rd
The following example demonstrates this argument
for Linux for simultaneously running remote updates on servers 10.6.9.58
and 10.0 8.137:
export UXSPI_MULTIPLE_INSTANCE=1
uxspi500.rhel5 up --remote=10.6.9.58 --remote-user=root
--remote-password=passw0rd > log1.txt 2>err1.txt &
uxspi500.rhel5 up --remote=10.0 8.137 --remote-user=root
--remote-password=passw0rd > log2.txt 2>err2.txt &
- Cancelling a remote UXSPI instance
might cancel other instances of UXSPI
If
you use a remote UXSPI that is
started by using the --remote option or from a third
party connection package such as Windows Remote Desktop Connection,
it cannot detect another UXSPI instance
running on the same remote system. Running multiple instances on the
same system is supported; however, clicking Cancel from
the GUI terminates all instances of UXSPI running
on the remote system.
Workaround
It is preferred
that you not run multiple instances of UXSPI on the
same remote system. If you do run multiple instances, manually check
to see whether any other administrators are running UXSPI before
clicking Cancel.
- Acquisition of the latest updates for a new machine type
does not update the UXSPI supported
machine types list
- The list of supported machine types in
the UXSPI GUI
includes all machine types supported at the time UXSPI was released.
New machine types are added to the list when an UpdateXpress System Pack is released for
the new machine type, or when the installer is updated. Acquiring
updates for a new machine type does not update the supported machine
types list in the GUI.
Workaround
Acquire the UpdateXpress System Pack for the new machine
type, restart the GUI to update the supported machine types list,
and then acquire the latest updates for the new machine type.
- Unable to execute UXSPI from a
USB key
- Some Linux operating systems (for example, SLES 10)
automatically mount USB devices with the noexec parameter.
This parameter disallows any user from running a program directory
from the mounted device.
Workaround
To run a file from
a USB device in this configuration, either copy the entire UXSP to your
hard disk drive and execute from that location, or remount the USB
device with the exec parameter. You can accomplish
the second option by first unmounting the USB device by issuing: umount
/mnt/usbkey as root (assuming /mnt/usbkey is
the mount point of the USB device). You can then remount the device
by specifying the mount command with the exec parameter.
For example: mount /dev/sdb1 /mnt/usbkey -o exec).
- Linux drivers are not active immediately
- The
Linux device drivers require activation. UXSPI loads
the new driver into the file system, but the operating system does
not use the new driver until it is loaded.
Workaround
To
modify this behavior, remove the existing driver with the rmmod command
and load the new driver with the modprobe command.
Alternatively, after rebooting the system the new driver is active.
- Linux LSI Logic SCSI 1020/1030/1064/1068 Controllers
are not detected after install
The
Linux device drivers require activation. UXSPI loads
the new driver into the file system, but the operating system does
not use the new driver until it is loaded.
Workaround
The
mptctl driver must be loaded. Run the lsmod command
to verify that mptcl is loaded. If it is not loaded, run the following
command to load the driver: modprobe mptctl.
- Linux version of UXSPI requires
compatibility libraries
- The 64-bit UXSPI requires
the compatibility libraries. However, the compatibility libraries
are not installed by default in RHEL4. Therefore, when you execute
the installer, it returns an error stating the library file is missing.
Workaround
Ensure
that you install the legacy software development packages.
- The path passed to the local path argument (-l or --local)
must not exceed 234 characters
- The local path argument cannot
exceed 234 characters
Workaround
Copy UpdateXpress System Pack to a directory
that is less than 234 characters.
- Firmware updates for the Broadcom network card for Linux
on CD/DVD and USB-Key bootable-media are not applied when the network
card is not up and active
- On Linux, a Broadcom network interface
controller must be up and active for firmware updates to be applied.
Also, on Linux and when updating from the bootable-media, each network
port must be connected to a switch or router.
Workaround
Ensure
the network interface controller that you are updating is up and active
for each port and connected to a switch or a router.
- UXSPI does
not always start on Linux systems
- In rare cases UXSPI might
fail to successfully start on Linux. In this case, the following error
message is sent to stderr:
----------------------------------------------------------
WARNING! This package doesn't appear to match your system.
It is likely that it will not properly execute.
The following information was determined for your system:
distribution = Red Hat
release = 4
processor architecture = Intel 64-bit"
----------------------------------------------------------
- Distribution, release, and processor architecture can vary and
match the Linux system. The installer will return an error code of
1.
Workaround
Restart UXSPI. It will
succeed the next time.
- USB key fails on RHEL5
- When a USB key is inserted
on RHEL5, by default it is mounted as noexec. noexec means
no application can run, including UXSPI.
Workaround
Override
the default
noexec mount option. For example,
mount a USB key device of /dev/sdc1 as /media/disk. To do so, perform
the following steps:
umount /dev/sdc1
mkdir /media/disk
mount -o exec /dev/sdc1 /media/disk
- User Account Control (UAC) on Windows Vista and Windows
Server 2008 prevents the installer from running without popup windows
- UAC is a security control that normally prompts you before running
the application at a privileged level on Windows Vista and Windows
Server 2008.
Workaround
To disable this feature for UXSPI, launch lnvgy_utl_uxspi_10.6_winsrvr_32-64.exe at
the command prompt with elevated privileges by completing the following
steps.
- Right-click lnvgy_utl_uxspi_10.6_winsrvr_32-64.exe and
select Run as Administrator.
- At the UAC prompt command window, click Yes .
UXSPI is
launched with a full administrator security token.
- Broadcom firmware is not detected or updated from CD
or DVD bootable-media on a IBM System x3550 system
- On anIBM System x3550
system, bootable-media on a CD or DVD might not detect the Broadcom
firmware version or successfully apply the firmware update.
Workaround
Use
a USB key instead of CD and DVD bootable-media, or ensure the Baseboard
Management Controller (BMC) is updated to version 1.27 build level
GFBT43A or later and then reboot the system.
- Unable to boot from USB Key bootable media on systems
with onboard SATA drives
- Systems that only support onboard
SATA drives, such as IBM System x336 andIBM System x306m, fail
to boot from the USB Key bootable media. However, systems using ServeRAID
adapters, or with LSI onboard 1064 or higher, do not experience this
problem.
Workaround
Create a CD bootable media and
apply the firmware updates from CD instead from the USB key.
- Booting from USB Key bootable media on a IBM System x3755 might
display video error messages
- When booting from USB Key bootable
media on a IBM System x3755,
you might see video error messages about the video resolution. The
error is displayed for 30 seconds unless you press the Enter key.
Workaround
Ignore
these error messages.
- Bootable media might not display all updates in the list
view
- The Bootable media Text User Interface (TUI) might not
display all the updates in the list view when the total number of
updates in the list view exceeds the size of the display screen. This
is particularly true for the IBM System x3755, which
displays a small screen size in the Bootable media TUI mode.
Workaround
Toggle
to see the full update detail list using the Full View selection.
- Additional requirements for Windows 2003 remote server
updates in IPv6 networks
- To perform remote server updates
for a Windows 2003 server in an IPv6 network, you must perform the
following steps:
- Set up the IPv6 network on the target server. Refer to Step-by-Step
Guide for Setting Up IPv6 in a Test Lab at: 11edd39551d7&displaylang=en
- Enable file sharing connections over the IPv6 on the target server.
To do this, add a key named DisableStrictNameChecking to
the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters,
with type REG_DWORD with a value=1.
- DSA (diags)
firmware is not always installed if the IMM is a previous version
- Because the DSA firmware
update is run before the IMM firmware update, if the IMM firmware
is an older previous version, the DSA firmware
update fails.
Workaround
Run the update twice. The
first update will bring the IMM firmware to the current level, which
allows the second update to update the DSA firmware.
A reboot is not required between the updates.
- Update of IBM HBA/LSI
onboard 6Gb firmware exits CLI
- When using the UXSPI CLI to
update the IBM HBA/LSI
onboard 6Gb firmware in Linux distributions (RHEL4 and RHEL5), UXSPI exits
without an Installation Successful message after performing
this update. The SAS firmware is installed correctly, but the updates
which follow (firmware and drivers for other devices in the system),
are not executed.
- This issue does not affect the UXSPI GUI or
the individual update for the IBM HBA/LSI
onboard 6Gb adapter.
- Full corequisite checking is not performed when using
the CLI
- When specifying update packages from the command line, UXSPI does not
perform full checking of corequisite packages. Specifically, while
both prerequisites and corequisites are checked for a current package,
if a package that is a prerequisite of the current package also has
a corequisite, the corequisite is not checked. In rare instances,
this can cause the update to fail. This issue does not affect the UXSPI GUI.
Workaround
To
avoid this issue, manually select any corequisite packages required
by packages that are prerequisites of the one you are installing.
Alternately, you can use the GUI.
- RHEL 6 requires installation of SOAPpy
- To function
properly on RHEL 6, UXSPI requires that the full-featured SOAP library
for Python (SOAPpy) be installed manually after operating system installation.
To install this library and all prerequisites manually, complete the
following steps.
- Insert the RHEL 6 installation CD.
- On the target system, select Add/Remove Software.
- In the search box, enter lib and click Search to
display a list of available libraries.
- Select the Full-Featured SOAP Library for Python (SOAPpy-0.11.6-11.el6)
and accept all of the prerequisites.
- Click Apply to install the files.
- Running UXSPI remotely
from a USB key using AMM can take an extremely long time to boot
- When running UXSPI from a
USB key using an AMM, boot times can be as long as 20-30 minutes.
This is a limitation of this scenario.
Workaround
To
avoid this problem, create a CD or DVD image of the boot media for
use in remote scenarios requiring the AMM.
- Undetected failure when two clients update the same VMware
ESXi target
- When separate UXSPI clients
attempt to remotely update the same VMware ESXi target system, both
updates fail, but no error is reported.
Workaround
Allow
only one UXSPI client
to perform a remote update to a VMware ESXi system at a time.
- UXSPI fails
to update the DSA package
- UXSPI fails
to update the DSA package
when the Diagnostics option is set from the
Boot Options menu in uEFI.
Workaround
Remove Diagnostics from
the Boot Options menu and AC-Cycle the system before flashing DSA with UXSPI. You can
also restart the system and verify that Diagnostics is
not in Boot Options before flashing DSA.
- UXSPI does
not support uploading a directory to the TFTP server
- Due to
the limitation of the TFTP server, UXSPI does not
support uploading a directory to the TFTP server. Therefore, if the
payload of the IO module firmware is a directory, UXSPI does not
support updating it automatically using TFTP server.
Workaround
Upload
the directory to the TFTP server manually and then use the --io-file option
to update the firmware. Alternatively, use the FTP or SFTP server.
- UXSPI fails
to update the device driver for the Flex System FC5022
2-port 16Gb FC Adapter in CLI mode
- UXSPI fails
to update the device driver for the Flex System FC5022
2-port 16Gb FC Adapter in CLI mode on Windows.
Workaround
Update
the device driver with UXSPI in GUI
mode.
- UXSPI sometimes
fails to update IMM on vSphere 5.0, 5.0 U1, and 5.1
- UXSPI sometimes
fails to update IMM on vSphere 5.0, 5.0 U1, and 5.1 due to the operation
system IPMI deadlock issue on vSphere 5.0, 5.0 U1, and 5.1. vSphere
5.1 U1 and 5.0 U2 are preferred.