Reposting: Unable to Update Integrated Management Module (IMM) firmware

Question

This post was originally posted on IBM’s developerWorks public forum (https://www.ibm.com/developerworks/community/forums/html/topic?id=0e1070ab-fbdc-4aa0-b9ea-3f9e391759...  The following is a summary of the post issue and the response.
Issue:
I'm using the UpdateXpress System Pack Installer to update the Integrated Management Module (IMM) firmware on my System X server (model 7915) running Windows Server 2012 R2 Server Core.
When I run the command to install the update (ibm_utl_uxspi_9.51_winsrvr_32-64.exe up -l "\\server\share" -m 7915) and it gets to the point where it is ready to install the IMM firmware update, it fails with the message "Unable to ping through IMM" and then references a log file.  According to the log file, the system is trying to ping "169.254.95.118" which is not the pre configured static IP address on the IMM interface.
I am able to remotely ping the static IP that I've configured and I'm able to log into the IMM web interface. Everything appears to be working correctly with the IMM, except that this UpdateXpress installer is not picking up the configured IMM’s static address.
Solution:
The UpdateXpress System Pack installer does not use the Integrated Management Module (IMM)'s interface and it will try to contact the card via the USB-LAN interface via the OS. The 169 address is the DHCP address assigned by the OS to the USB-LAN card (you should see it in a list of interfaces). When you run the installer from the OS, it will search for the card via the USB-LAN and if it's blocked it will fail.  Any security restrictions on that interface or a firewall running on it will block it.
Since you can login to the card itself, you can always just upload the IMM firmware package (.exe or .bin) to the card directly via its own Firmware Update function.  This option is on the left about halfway down the menu. All you need to do is to give it the file path to where the package is located and follow the prompts for the upload and update.
Or, you can remove the static IP you assigned and set it back to DHCP.  Typically the installer will find the interface, enable it as needed, and then an IP address will get assigned automatically.

Answer 1

Hi Lawrence,
Sorry for the delay, i was Out of station. Also, one info i have to share with you, there is an another server with same version (7.5.7601)
and is getting FEP updates without any fail.
I haven't rebooted the server because it is critical server, so i have applied the remaining and here is the logs.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
2014-03-02 21:57:00:057
Triggering AU detection through DetectNow API
2014-03-02 21:57:00:057
Can not perform non-interactive scan if AU is interactive-only
2014-03-02 22:01:14:641
WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2014-03-02 22:01:14:641
WARNING: PTError: 0x80244019
2014-03-02 22:01:14:641
WARNING: GetConfig_WithRecovery failed: 0x80244019
2014-03-02 22:01:14:641
WARNING: RefreshConfig failed: 0x80244019
2014-03-02 22:01:14:641
WARNING: RefreshPTState failed: 0x80244019
2014-03-02 22:01:14:641
WARNING: PTError: 0x80244019
2014-03-02 22:01:14:641
WARNING: Reporter failed to upload events with hr = 80244019.
2014-03-02 22:26:16:148
WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2014-03-02 22:26:16:148
WARNING: PTError: 0x80244019
2014-03-02 22:26:16:148
WARNING: GetConfig_WithRecovery failed: 0x80244019
2014-03-02 22:26:16:148
WARNING: RefreshConfig failed: 0x80244019
2014-03-02 22:26:16:148
WARNING: RefreshPTState failed: 0x80244019
2014-03-02 22:26:16:148
WARNING: PTError: 0x80244019
2014-03-02 22:26:16:148
WARNING: Reporter failed to upload events with hr = 80244019.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jay :)