cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JayCX
Ctrl-Alt-Del
Posts: 6
Registered: ‎02-06-2019
Location: DE
Views: 555
Message 1 of 8

Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

Hello,

 

I have troube flashing an recent BIOS and IMM2 to an IBM X3550 M4 7914 PKK.

 

Downloading the IMM Firmware (IMM2:6.0,6.6,7.0; UEFI 2.6,2.8) from the IBM Site and Flashing it via IMM2 returns "The uploaded file is not a valid update firmware file")imm2_upd.PNG

 

 

 

 

What i tried:

Creating image with

BOMC 9.41,9.64,10.1,11.3,11.4, selected 7914 downloading the Firmware (several times)

and flashing it returns "The Update is not meant for this system"

But it flashed the Raidcontroller Firmware without issues.

 

So i reinstalled the system with Windows and tried UXSPI 10.1 to Download and Install the Firmware UXP Package but that returns also

"Error flashing firmware: 0x26 (The update is not meant for this system.)"

 

see log:

 

Spoiler
FDR_[Status] 2/1/2019  16:45:38 Start of command miniunz.exe -xo ibm_fw_imm2_1aoo82e-6.60_anyos_noarch.uxz -d ibm_fw_imm2_1aoo82e-6.60_anyos_noarch :
MiniUnz 1.01b, demo of zLib + Unz package written by Gilles Vollant

more info at http://www.winimage.com/zLibDll/unzip.html



ibm_fw_imm2_1aoo82e-6.60_anyos_noarch.uxz opened

 extracting: imm2_1aoo82e-6.60.upd

 extracting: OpenSourceNotices.html

 extracting: imm.mib

 extracting: immalert.mib

 extracting: immRegistries.zip

 extracting: payload.xml

End of command miniunz.exe log messages.
FDR_[Status] 2/1/2019  16:45:38 find the upd file : imm2_1aoo82e-6.60.upd
FDR_[Status] 2/1/2019  16:45:38 The size of .upd file is: 76293646
FDR_[Verbose] 2/1/2019  16:45:38 After changing, current working directory is iflash
FDR_[Verbose] 2/1/2019  16:45:38 UpdateController::RunAgnosticUpdate(): Parameter(s) --package
FDR_[Verbose] 2/1/2019  16:45:38 UpdateController::RunAgnosticUpdate(): Parameter(s) ..\ibm_fw_imm2_1aoo82e-6.60_anyos_noarch\imm2_1aoo82e-6.60.upd
FDR_[Verbose] 2/1/2019  16:45:38 UpdateController::RunAgnosticUpdate(): Parameter(s) --user=Support
FDR_[Verbose] 2/1/2019  16:45:38 UpdateController::RunAgnosticUpdate(): Parameter(s) --password=****************
FDR_[Verbose] 2/1/2019  16:45:38 UpdateController::RunAgnosticUpdate(): Parameter(s) --force
FDR_[Debug] 2/1/2019  16:45:38 SpawnProcess: process iflash64.exe
FDR_[Status] 2/1/2019  16:45:59 Start of update iflash64.exe log messages (if any):
IBM Command Line IMM Flash Update Utility v2.02.18

Licensed Materials - Property of IBM

(C) Copyright IBM Corp. 2009 - 2015  All Rights Reserved.



Pinging IMM IP address 169.254.95.118 .....OK

Connected to IMM at IP address 169.254.95.118.

Update package firmware type: IMM2

Update package build level:   1AOO82E

Target's current build level: 1AOE70I



Node 0: The IMM is preparing to receive the update.




Node 0: Transferring image: 0%

Node 0: The specified update is not meant for this system.



Error flashing firmware: 0x26 (The update is not meant for this system.)

Recommended action :

Please refer to Best Practice Firmware Update Guide from

http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000020&lndocid=MIGR-5082923

So i tried it again with UXSPI 9.63 that didn't recognize the UXP Packs i downloaded before but after I klicked "install latest [...]" it also failed with "Node 0: The specified update is not meant for this system."

 

Log:

Spoiler
DR_[Verbose] 2/6/2019  10:16:24 [TimeStamp][UpdateController:Smiley Frustratedtart] update procedure start
FDR_[Verbose] 2/6/2019  10:16:24 [TimeStamp][UpdateController::CopyUpdate] ibm_fw_imm2_1aoo86d-7.00_anyos_noarch CopyUpdate start
FDR_[Verbose] 2/6/2019  10:16:24 UpdateController::CopyUpdate() Succeeded to copy update files to temporary directory. The working directory is C:\Users\Administrator\Desktop\x3550-fw-upgrade\\ibm_fw_imm2_1aoo86d-7.00_anyos_noarch.uxz
FDR_[Verbose] 2/6/2019  10:16:24 [TimeStamp][UpdateController::CopyUpdate] ibm_fw_imm2_1aoo86d-7.00_anyos_noarch CopyUpdate end
FDR_[Verbose] 2/6/2019  10:16:24 [TimeStamp][UpdateController::RunUpdate] ibm_fw_imm2_1aoo86d-7.00_anyos_noarch update start
FDR_[Status] 2/6/2019  10:16:24 This is an OS agnostic update.
FDR_[Status] 2/6/2019  10:16:24 UpdateController::CheckAgnosticArgs() arguments for updating IMM : --user=Support --password=****************
FDR_[Debug] 2/6/2019  10:16:24 SpawnProcess: process miniunz.exe
FDR_[Status] 2/6/2019  10:16:25 Start of command miniunz.exe -xo ibm_fw_imm2_1aoo86d-7.00_anyos_noarch.uxz -d ibm_fw_imm2_1aoo86d-7.00_anyos_noarch :
MiniUnz 1.01b, demo of zLib + Unz package written by Gilles Vollant

more info at http://www.winimage.com/zLibDll/unzip.html



ibm_fw_imm2_1aoo86d-7.00_anyos_noarch.uxz opened

 extracting: imm2_1aoo86d-7.00.upd

 extracting: OpenSourceNotices.html

 extracting: imm.mib

 extracting: immalert.mib

 extracting: immRegistries.zip

 extracting: payload.xml

End of command miniunz.exe log messages.
FDR_[Status] 2/6/2019  10:16:25 find the upd file : imm2_1aoo86d-7.00.upd
FDR_[Status] 2/6/2019  10:16:25 The size of .upd file is: 76406286
FDR_[Verbose] 2/6/2019  10:16:25 Set the environment variable UXSPI_IFLASH_ERRLOG=C:\IBM_Support\.IFLASH_ERR_WIN-DBPO2K0HIC0_7914_20190206100753.773000+-60.log
FDR_[Verbose] 2/6/2019  10:16:25 Set the environment variable UXSPI_IFLASH_ERRMSG=C:\IBM_Support\.IFLASH_OUT_WIN-DBPO2K0HIC0_7914_20190206100753.773000+-60.log
FDR_[Verbose] 2/6/2019  10:16:25 Set the environment variable UXSPI_IFLASH_MSG=C:\IBM_Support\.IFLASH_MSG_WIN-DBPO2K0HIC0_7914_20190206100753.773000+-60.log
FDR_[Verbose] 2/6/2019  10:16:25 After changing, current working directory is iflash
FDR_[Verbose] 2/6/2019  10:16:25 UpdateController::RunAgnosticUpdate(): Parameter(s) --package
FDR_[Verbose] 2/6/2019  10:16:25 UpdateController::RunAgnosticUpdate(): Parameter(s) ..\ibm_fw_imm2_1aoo86d-7.00_anyos_noarch\imm2_1aoo86d-7.00.upd
FDR_[Verbose] 2/6/2019  10:16:25 UpdateController::RunAgnosticUpdate(): Parameter(s) --user=Support
FDR_[Verbose] 2/6/2019  10:16:25 UpdateController::RunAgnosticUpdate(): Parameter(s) --password=****************
FDR_[Verbose] 2/6/2019  10:16:25 UpdateController::RunAgnosticUpdate(): Parameter(s) --force
FDR_[Debug] 2/6/2019  10:16:25 SpawnProcess: process iflash64.exe
FDR_[Status] 2/6/2019  10:16:44 Start of update iflash64.exe log messages (if any):
IBM Command Line IMM Flash Update Utility v2.02.12

Licensed Materials - Property of IBM

(C) Copyright IBM Corp. 2009 - 2014  All Rights Reserved.



Pinging IMM IP address 169.254.95.118 .....OK

Connected to IMM at IP address 169.254.95.118.

Update package firmware type: IMM2

Update package build level:   1AOO86D

Target's current build level: 1AOE70I



Node 0: The IMM is preparing to receive the update.




Node 0: Transferring image: 0%
Node 0: Transferring image: 2%

Node 0: The specified update is not meant for this system.



Error flashing firmware: 0x26 (The update is not meant for this system.)

Recommended action :

Please refer to Best Practice Firmware Update Guide from

http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000020&lndocid=MIGR-5082923

Dumped iflash internal trace to logfile C:\IBM_Support\.IFLASH_ERR_WIN-DBPO2K0HIC0_7914_20190206100753.773000+-60.log.

 

I verified that Comands via USB is enabled in UEFI

 

For laughs and giggles i tried to flash DSA, same version, via IMM2 and that did work.

 

I wanted to try BOMC 9.66 but it Reports, that the IBM Repo isn't available.

 

EDIT:

 

I tried to Upgrade with UXSPI 10.5 and i get the Error, "Unknown Failure: [...]"

uxspi10-5-error.PNG

 

I tried UXSPI 10.2 and IMM2 6.6/UEFI 2.6 (redownloaded that) and get the same Error:

Log:

Spoiler
FDR_[Status] 2/6/2019  15:47:17 find the upd file : imm2_1aoo82e-6.60.upd
FDR_[Status] 2/6/2019  15:47:17 The size of .upd file is: 76293646
FDR_[Verbose] 2/6/2019  15:47:17 After changing, current working directory is iflash
FDR_[Verbose] 2/6/2019  15:47:17 UpdateController::RunAgnosticUpdate(): Parameter(s) --package
FDR_[Verbose] 2/6/2019  15:47:17 UpdateController::RunAgnosticUpdate(): Parameter(s) ..\ibm_fw_imm2_1aoo82e-6.60_anyos_noarch\imm2_1aoo82e-6.60.upd
FDR_[Verbose] 2/6/2019  15:47:17 UpdateController::RunAgnosticUpdate(): Parameter(s) --user=Support
FDR_[Verbose] 2/6/2019  15:47:17 UpdateController::RunAgnosticUpdate(): Parameter(s) --password=****************
FDR_[Verbose] 2/6/2019  15:47:17 UpdateController::RunAgnosticUpdate(): Parameter(s) --force
FDR_[Debug] 2/6/2019  15:47:17 SpawnProcess: process iflash64.exe
FDR_[Status] 2/6/2019  15:47:40 Start of update iflash64.exe log messages (if any):
IBM Command Line IMM Flash Update Utility v2.02.18

Licensed Materials - Property of IBM

(C) Copyright IBM Corp. 2009 - 2015  All Rights Reserved.



Pinging IMM IP address 169.254.95.118 .....OK

Connected to IMM at IP address 169.254.95.118.

Update package firmware type: IMM2

Update package build level:   1AOO82E

Target's current build level: 1AOE70I



Node 0: The IMM is preparing to receive the update.




Node 0: Transferring image: 0%
Node 0: Transferring image: 1%

Node 0: The specified update is not meant for this system.



Error flashing firmware: 0x26 (The update is not meant for this system.)

Recommended action :

Please refer to Best Practice Firmware Update Guide from

http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000020&lndocid=MIGR-5082923

Dumped iflash internal trace to logfile C:\Lenovo_Support\.IFLASH_ERR_WIN-DBPO2K0HIC0_7914_20190206143306.750000+-60.log.

I tried to flash the UEFI 1.70 (same Version as current) with UXSPI 9.63  and also get the not menat for this system Error.

963-uefi170.PNG

That makes no sense to me. I let the UXSPI detect and download the Updates.

 

I'd gladly take suggestions here. What can I do to resolve this?

 

 

JayCX
Ctrl-Alt-Del
Posts: 6
Registered: ‎02-06-2019
Location: DE
Views: 502
Message 2 of 8

Re: Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

An interesting thing is, that i researched the firmware SN/No. installied is: 1.70 D7EG40YUS and the UXSPI 9.63 detected Machine Type 7914 and Downloaded UEFI 1.70 Y5E140A AND UEFI 1.70 VVE142A and UEFI 1.70 D7E140Y but after i tried to install UEFI 1.70 via UXSPI it stated, it isnt for my System.

 

also bump

Lenovo Employee arossett
Lenovo Employee
Posts: 160
Registered: ‎08-14-2018
Location: US
Views: 490
Message 3 of 8

Re: Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

Hello there is quite a bit of information you've posted. I apolgize if i missed the following questions from the post. 

 

Can you let me know what current version of UEFI/IMM firmware you are using on the x3550 M4?

 

If possible from the IMM could you post a pic of the Server Firmware tab?

 

It looks like your currently using UEFI 1.70, but I'm a bit unclear from everything that has been tried. 

 

Also by chance has the motherboard in this server ever been replaced? It may be possible the VPD did not get set correclty. If this is the case this could be corrected using onecli.

 

Here is an article that covers this. https://support.lenovo.com/us/en/solutions/HT507532

 

Before you go through the artilce  please verify that the information is set correclty using the following commands. You can DM me the output so you do not have to post this publicly. 

 

Example: issue the following command to check the settings

OneCli.exe config show SYSTEM_PROD_DATA

 

Last but not least could you send me the C:\IBM_Support\.IFLASH_ERR_WIN-DBPO2K0HIC0_7914_20190206100753.773000+-60.log.

 

I would like to review this for further information. 

Highlighted
JayCX
Ctrl-Alt-Del
Posts: 6
Registered: ‎02-06-2019
Location: DE
Views: 475
Message 4 of 8

Re: Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

Hello, arosett, thank you very much for your reply!

 

Yes, i tried to update from UEFI 1.70 and IMM 5.41

See Screenshot:

imm_fw.PNG

 

Onecli returns:

 

Spoiler
c:\lnvgy_utl_lxce_onecli01a-2.4.1_winsrv_x86-64>OneCli.exe config show SYSTEM_PROD_DATA

Lenovo XClarity Essentials OneCLI lxce_onecli01a-2.4.1
Licensed Materials - Property of Lenovo
(C) Copyright Lenovo Corp. 2013-2018 All Rights Reserved

OneCLI License Agreement and OneCLI Legal Information can be found at the following location:
    "c:\lnvgy_utl_lxce_onecli01a-2.4.1_winsrv_x86-64\Lic"

If the parameters you input includes password, please Note that:
* The password must consist of a sequence of characters from `0-9a-zA-Z_-+.$%@!^&*()=` set
* Use "" to quote when password parameters include special characters
* Do not use reserved characters in path name when parameter contains path
This is an older system and supported with 1.x version of the XClarity Essentials ASU tool
Translated ASU Command=show SYSTEM_PROD_DATA
Lenovo Advanced Settings Utility version 10.5.94O
Licensed Materials - Property of Lenovo
(C) Copyright Lenovo Corp. 2014-2018 All Rights Reserved
Successfully discovered the IMM via SLP.
Discovered IMM at IP address 169.254.95.118
Unable to validate userid/password on IMM.
Please make sure input the correct userid/password with supervisor authority level.
Attempting to configure usb-lan.
IMM LAN-over-USB device 0 enabled successfully.
Successfully discovered the IMM via SLP.
Discovered IMM at IP address 169.254.95.118
Unable to validate userid/password on IMM.
Please make sure input the correct userid/password with supervisor authority level.
Unable to connect to IMM via LAN : Connect using LAN failed..
Connected via IPMI device driver (KCS interface)
SYSTEM_PROD_DATA.SysInfoProdName=7914PKK
SYSTEM_PROD_DATA.SysInfoProdIdentifier=IBM System x3550 M4:
SYSTEM_PROD_DATA.SysInfoSerialNum=<sn>
SYSTEM_PROD_DATA.SysInfoUUID=<uuid>
SYSTEM_PROD_DATA.SysInfoUDI=
SYSTEM_PROD_DATA.SysEncloseAssetTag=

UID and SN matches the displayed Numbers in IMM, i just deleted them.

sysinfo.PNG

But that did only work after setting the absolute Path in Global.Config from OneCli to ASU:

Spoiler
[...]
#To set ASU path, you should first extract "asu.exe" out of the official ASU executable wrapper(e.g, lnvgy_utl_asu_asut90e-10.1_windows_x86-64.exe)
#then, change the value of "ASU_PATH" from "NONE"  to the absolute path to where you put "asu.exe" extracted above
#Do not set the path to the proxy tool inside XClarity Essentials OneCLI
#default value is "NONE"
ASU_PATH=C:\lenovo-asu\asu64.exe
#ASU_PATH=NONE
[...]

The mentioned Log may be already deleted but I will send you an recent one.

 

Thanks in Advance!

 

JayCX
Ctrl-Alt-Del
Posts: 6
Registered: ‎02-06-2019
Location: DE
Views: 416
Message 5 of 8

Re: Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

Out of spite i tried to set the Systemid to 7914 instead of 7914PKK with onecli, but that just crashed onecli.

 

All Messages and Errors suggest, that i try to flash the wrong firmware. But if i type the SN in Lenovo Support it says i can get the uefi and imm only on the IBM site and returns this Link: https://www-945.ibm.com/support/fixcentral/systemx/selectFixes?parent=System%20x3550%20M4&product=ib...

Where i clicked "uefi" and dl.

Then i have to insert my IBM ID and then i get

 The fix ids are null.
Selected Fix ID(s): []
Order State History: [Initial]
Order Time: Fri Feb 15 16:52:21 UTC 2019
Entry URL: https://www-945.ibm.com/support/fixcentral/systemx/downloadFixes
HSB Order ID: 

so, i tried it again and got:

ibm.PNG

i click download and mount it.


Then i open UXSPI 9.63 (it recognizes machine type 7914 and OS) and klick update local machine, look in folder: mounted cdrom, use latest.

It then compares the update says i need to update - wants the 4.31 IMM2 present (i have installed IMM2 5.41 )

(out of caution i klicked, target 2nd FW Bank)

I didn't insert an IPMI/IMM2 Login

I click next and it says running, till

I get the same Error again.

ibm-uefi963.PNG

It Shows this in the Errorlog:

Spoiler
[...]
FDR_[Status] 2/15/2019  18:6:41 This is an OS agnostic update.
FDR_[Status] 2/15/2019  18:6:41 UpdateController::CheckAgnosticArgs() arguments for updating uEFI : --backup
FDR_[Debug] 2/15/2019  18:6:41 SpawnProcess: process miniunz.exe
FDR_[Status] 2/15/2019  18:6:41 Start of command miniunz.exe -xo ibm_fw_uefi_d7e166d-2.80_anyos_32-64.uxz -d ibm_fw_uefi_d7e166d-2.80_anyos_32-64 :
MiniUnz 1.01b, demo of zLib + Unz package written by Gilles Vollant

more info at http://www.winimage.com/zLibDll/unzip.html



ibm_fw_uefi_d7e166d-2.80_anyos_32-64.uxz opened

 extracting: ibm_fw_uefi_d7e166d-2.80_anyos_32-64.upd

 extracting: payload.xml

End of command miniunz.exe log messages.
FDR_[Status] 2/15/2019  18:6:41 find the upd file : ibm_fw_uefi_d7e166d-2.80_anyos_32-64.upd
FDR_[Status] 2/15/2019  18:6:41 The size of .upd file is: 3825788
FDR_[Verbose] 2/15/2019  18:6:41 Set the environment variable UXSPI_IFLASH_ERRLOG=C:\IBM_Support\.IFLASH_ERR_WIN-DBPO2K0HIC0_7914_20190215180130.117000+-60.log
FDR_[Verbose] 2/15/2019  18:6:41 Set the environment variable UXSPI_IFLASH_ERRMSG=C:\IBM_Support\.IFLASH_OUT_WIN-DBPO2K0HIC0_7914_20190215180130.117000+-60.log
FDR_[Verbose] 2/15/2019  18:6:41 Set the environment variable UXSPI_IFLASH_MSG=C:\IBM_Support\.IFLASH_MSG_WIN-DBPO2K0HIC0_7914_20190215180130.117000+-60.log
FDR_[Verbose] 2/15/2019  18:6:41 After changing, current working directory is iflash
FDR_[Verbose] 2/15/2019  18:6:41 UpdateController::RunAgnosticUpdate(): Parameter(s) --package
FDR_[Verbose] 2/15/2019  18:6:41 UpdateController::RunAgnosticUpdate(): Parameter(s) ..\ibm_fw_uefi_d7e166d-2.80_anyos_32-64\ibm_fw_uefi_d7e166d-2.80_anyos_32-64.upd
FDR_[Verbose] 2/15/2019  18:6:41 UpdateController::RunAgnosticUpdate(): Parameter(s) --backup
FDR_[Verbose] 2/15/2019  18:6:41 UpdateController::RunAgnosticUpdate(): Parameter(s) --force
FDR_[Debug] 2/15/2019  18:6:41 SpawnProcess: process iflash64.exe
FDR_[Status] 2/15/2019  18:6:55 Start of update iflash64.exe log messages (if any):
IBM Command Line IMM Flash Update Utility v2.02.12

Licensed Materials - Property of IBM

(C) Copyright IBM Corp. 2009 - 2014  All Rights Reserved.



Pinging IMM IP address 169.254.95.118 .....OK

Unable to validate userid/password on IMM at IP address 169.254.95.118.

Connecting via IPMI device driver (KCS interface)....



Update package firmware type: uEFI

Update package build level:   D7E166D

Target's current backup build level: D7EG34E



Node 0: The IMM is preparing to receive the update.




Node 0: Transferring image: 0%
Node 0: Transferring image: 11%

Node 0: The specified update is not meant for this system.



Error flashing firmware: 0x26 (The update is not meant for this system.)

Recommended action :

Please refer to Best Practice Firmware Update Guide from

http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000020&lndocid=MIGR-5082923

Dumped iflash internal trace to logfile C:\IBM_Support\.IFLASH_ERR_WIN-DBPO2K0HIC0_7914_20190215180130.117000+-60.log.


FDR_[Status] 2/15/2019  18:6:55 End of command iflash64.exe log messages.
FDR_[Status] 2/15/2019  18:6:55 The following is the error log from iflash :
FDR_[Status] 2/15/2019  18:6:55 18:06:41  Log(20) SignalHandler.C::?InitializeSignals@@YAHP6A_NXZP6AXXZ111@Z::[106] | No Error setting signal Handlers

[...]
Node: 0

Primary: Yes

KCS control: Yes

LAN confirmed: No

IP: 169.254.95.118

username: USERID

18:06:42  Log(30) FlashIBMC.C::?FlashIBMC@@YAHAEAUibmc_options_struct@@@Z::[1060] | performing update on options struct

IP:

Interface:

use TFTP: 0

use SFTP: 0

attended mode: 1

override mode: 1

backUp: 1

save: 0

restore: 0

no reboot: 0

reboot: 0

use KCS: 0

username:

firmwareOverride:

updateFile: ..\ibm_fw_uefi_d7e166d-2.80_anyos_32-64\ibm_fw_uefi_d7e166d-2.80_anyos_32-64.upd
[...]
FDR_[Status] 2/15/2019  18:6:55 End of the error log from iflash
FDR_[Verbose] 2/15/2019  18:6:55 return to previous directory C:\Users\ADMINI~1\AppData\Local\Temp\2\PORTAB~2\WINDOW~1\image
FDR_[Verbose] 2/15/2019  18:6:55 Because this update failed 0 other updates will fail!
FDR_[Verbose] 2/15/2019  18:6:55 Failed to flash ESW update package ibm_fw_uefi_d7e166d-2.80_anyos_32-64 and need to capture FFDC.
FDR_[Warning] 2/15/2019  18:6:55 [FFDCCapturer] The UserID to set is empty so the default userid     and password are still in use.
FDR_[Debug] 2/15/2019  18:6:55 UpdateController:Smiley Frustratedet IMM UserID and Password to capture FFDC :  
FDR_[Verbose] 2/15/2019  18:6:55 [FFDCCapturer] StartCaptureFFDC start.
FDR_[Verbose] 2/15/2019  18:6:55 [FFDCCapturer] Get usb lan IMM IP and Check usb lan connection for node 0.
FDR_[Status] 2/15/2019  18:6:55 [UxliteImmUsbLan] GetLanOverUsbIMMIp for Node: 0
FDR_[Verbose] 2/15/2019  18:6:55 [FFDCCapturer] usb lan IMM IP:169.254.95.118
FDR_[Debug] 2/15/2019  18:6:55 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::EnableUsbLanDevice(), f_Node=0
FDR_[Verbose] 2/15/2019  18:6:55 [UxliteImmUsbLan] Enabling LAN-over-USB ...
FDR_[Debug] 2/15/2019  18:6:55 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::GetStat(), f_Node=0
FDR_[Status] 2/15/2019  18:7:1 [UxliteImmUsbLan] LAN-over-USB: Enabled.
FDR_[Debug] 2/15/2019  18:7:1 [UxliteImmUsbLan] <-- UxliteImmUsbLanCfg::GetStat(), rc=1
FDR_[Status] 2/15/2019  18:7:1 [UxliteImmUsbLan] LAN-over-USB is already enabled before.
FDR_[Debug] 2/15/2019  18:7:1 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::GetStat(), f_Node=0
FDR_[Status] 2/15/2019  18:7:7 [UxliteImmUsbLan] LAN-over-USB: Enabled.
FDR_[Debug] 2/15/2019  18:7:7 [UxliteImmUsbLan] <-- UxliteImmUsbLanCfg::GetStat(), rc=1
FDR_[Debug] 2/15/2019  18:7:7 [UxliteImmUsbLan] <-- UxliteImmUsbLanCfg::Enable(), rc=0
FDR_[Verbose] 2/15/2019  18:7:13 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::EnableUsbLanConn(), f_Node=0
FDR_[Verbose] 2/15/2019  18:7:13 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::EnableUsbLanConn(), host usb lan ip = 169.254.95.120
FDR_[Verbose] 2/15/2019  18:7:13 [UxliteImmUsbLan] Enabling LAN-over-USB connect...
FDR_[Error] 2/15/2019  18:7:19 [UxliteImmUsbLan] QueryUsbLanConnState get ULC_SUCCESS, No need to enable usb lan connect.
FDR_[Debug] 2/15/2019  18:7:19 [UxliteImmUsbLan] <-- UxliteImmUsbLanCfg::EnableUsbLanConn(), rc=0
FDR_[Verbose] 2/15/2019  18:7:19 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::EnableUsbLanConn(), host usb lan ip = 169.254.95.120
FDR_[Verbose] 2/15/2019  18:7:19 [FFDCCapturer] Successfully enable IMM USB Lan Connection.
FDR_[Verbose] 2/15/2019  18:7:19 [FFDCCapturer] Failed to connect via USB Lan so we will use KCS.
FDR_[Verbose] 2/15/2019  18:7:19 [FFDCCapturer] Succeeded to connect to IMM.
FDR_[Debug] 2/15/2019  18:7:19 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 10.
FDR_[Verbose] 2/15/2019  18:7:19 [FFDCCapturer] Succeeded to issue IPMI command to gather FFDC.
FDR_[Debug] 2/15/2019  18:8:19 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:8:19 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:24 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:8:24 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:29 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:8:29 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:8:29 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:8:29 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:34 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:8:34 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:39 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:8:39 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:8:39 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:8:39 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:44 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:8:44 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:49 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:8:49 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:8:49 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:8:49 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:54 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:8:54 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:8:59 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:8:59 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:8:59 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:8:59 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:4 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:9:4 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:9 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:9:9 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:9:10 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:9:10 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:15 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:9:15 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:20 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:9:20 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:9:20 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:9:20 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:25 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:9:25 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:30 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:9:30 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:9:30 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:9:30 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:35 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 2.
FDR_[Verbose] 2/15/2019  18:9:35 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:40 [FFDCCapturer] The completion code is 0, the length and content of the response are 0 0.
FDR_[Error] 2/15/2019  18:9:40 [FFDCCapturer] The response of IPMI command to query status is empty
FDR_[Debug] 2/15/2019  18:9:40 [FFDCCapturer] The completion code is 0, the length and content of the response are 2 2.
FDR_[Verbose] 2/15/2019  18:9:40 [FFDCCapturer] FFDC capturing is still in progress.
FDR_[Debug] 2/15/2019  18:9:45 [FFDCCapturer] The completion code is 0, the length and content of the response are 1 1.
FDR_[Verbose] 2/15/2019  18:9:45 [FFDCCapturer] The FFDC file has been generated successfully.
FDR_[Debug] 2/15/2019  18:9:45 [FFDCCapturer] The completion code is 0, the length of the response is 14.
FDR_[Verbose] 2/15/2019  18:9:45 [FFDCCapturer] Succeeded to get the info of sFTP server.
FDR_[Verbose] 2/15/2019  18:9:48 [SftpDownload] Succeeded to show file names in the specified directory.
FDR_[Verbose] 2/15/2019  18:9:48 [SftpDownload] There is a file 7914PKK_06CPCBD_imm2_190215-172414.tgz
FDR_[Verbose] 2/15/2019  18:9:51 [SftpDownload] Succeeded to show file names in the specified directory.
FDR_[Verbose] 2/15/2019  18:9:51 [FFDCCapturer] Succeeded to save FFDC file in the directory C:\IBM_Support\ffdc_20190215180130.117000+-60
FDR_[Status] 2/15/2019  18:9:51 Succeed to get FFDC and save it as file C:\IBM_Support\ffdc_20190215180130.117000+-60\7914PKK_06CPCBD_imm2_190215-172414.tgz
FDR_[Verbose] 2/15/2019  18:9:51 [TimeStamp][UpdateController::RunUpdate] ibm_fw_uefi_d7e166d-2.80_anyos_32-64 update end
FDR_[Verbose] 2/15/2019  18:9:51 [TimeStamp][UpdateController:Smiley Frustratedtart] update procedure end
FDR_[Status] 2/15/2019  18:9:51 IBM uEFI Flash Update completed with return code: 38
FDR_[Status] 2/15/2019  18:9:51 [UpdateController] Show messages after update.
FDR_[Debug] 2/15/2019  18:9:51 [UpdateController] --> ShowPostUpdateMsg()
FDR_[Verbose] 2/15/2019  18:9:51 ShowPostUpdateMsg(): Process uEFI reboot hint.
FDR_[Debug] 2/15/2019  18:9:51 ShowPostUpdateMsg(): uEFI update detected.
FDR_[Debug] 2/15/2019  18:9:51 ShowPostUpdateMsg(): uEFI update failed.
FDR_[Debug] 2/15/2019  18:9:51 [UpdateController] <-- ShowPostUpdateMsg()
FDR_[Status] 2/15/2019  18:9:51 Controller Update finished with errors.
FDR_[Status] 2/15/2019  18:9:51 Successfully write C:\IBM_Support\common_result.xml
FDR_[Verbose] 2/15/2019  18:9:51 log is C:\IBM_Support\UXSPI_WIN-DBPO2K0HIC0_7914_20190215180130.117000+-60.log
FDR_[Verbose] 2/15/2019  18:9:52 [TimeStamp][MainController::runLoop] Clean up work before Maincontroller exit start
FDR_[Status] 2/15/2019  18:9:52 MainController::runLoop(): UXSPI exited with the return code: 59
Status message: One or more updates did not install during deployment.  See %LOGFILE for details.


FDR_[Verbose] 2/15/2019  18:9:52 [TimeStamp][MainController::runLoop] Stop pmc service start
FDR_[Verbose] 2/15/2019  18:9:52 Stop pmc service.
FDR_[Verbose] 2/15/2019  18:9:52 [TimeStamp][MainController::runLoop] Stop pmc service end
FDR_[Debug] 2/15/2019  18:9:52 [MainController] Restore LAN-over-USB status.
FDR_[Debug] 2/15/2019  18:9:52 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::RestoreStat()
FDR_[Verbose] 2/15/2019  18:9:52 [UxliteImmUsbLan] Restoring LAN-over-USB status ...
FDR_[Debug] 2/15/2019  18:9:52 [UxliteImmUsbLan] --> UxliteImmUsbLanCfg::GetStat(), f_Node=0
FDR_[Status] 2/15/2019  18:9:59 [UxliteImmUsbLan] LAN-over-USB: Enabled.
FDR_[Debug] 2/15/2019  18:9:59 [UxliteImmUsbLan] <-- UxliteImmUsbLanCfg::GetStat(), rc=1
FDR_[Status] 2/15/2019  18:9:59 [UxliteImmUsbLan] Enabled all the time, needn't to restore.
FDR_[Debug] 2/15/2019  18:9:59 [UxliteImmUsbLan] <-- UxliteImmUsbLanCfg::RestoreStat()
FDR_[Status] 2/15/2019  18:9:59 Delete command.txt
-- DSA Log Closed ----------------------------

 If you have any further ideas, I would be pleased to hear them.

JayCX
Ctrl-Alt-Del
Posts: 6
Registered: ‎02-06-2019
Location: DE
Views: 307
Message 6 of 8

Re: Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

arosett wanted to test something and fix me up with an batch script to install the update anyway.

 

In the Meantime I tried my luck with a completely different Server (also 7914PKK) and BOMC 9.66 and failed.

 

In the logs there it seems to be an issue with the IMM authentication, so i created a new userSmiley Tongueassword with superuser access privileges and tried again...

...unfortunately without luck.

 

So still stuck.

Lenovo Employee arossett
Lenovo Employee
Posts: 160
Registered: ‎08-14-2018
Location: US
Views: 240
Message 7 of 8

Re: Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

Thanks Jay for all of the information as we have been speaking through PM. I am glad to see that the process that we came up with worked for you. 

JayCX
Ctrl-Alt-Del
Posts: 6
Registered: ‎02-06-2019
Location: DE
Views: 213
Message 8 of 8

Re: Trouble flashing IBM X3550 M4 7914 PKK UEFI and IMM2

Hi arosett,

 

thank you very very much again for your support!

He Said there will be an detailed KB article and he wants to link it here, when its ready. So in the meantime, if anybody else has this Problem, you can flash the Update via iflash64 and turn off the checks for it.

 

But you have to be very sure, what you flash and that it is really for your server, otherwise you can render it useless.

 

The procedure from arosett is:

[...]

To start things off on my local hard drive I created a folder called update C:\Update. This is where  I placed all downloaded files to try and keep things straight.  I also have made the assumption you have the IPMItool installed in your environment.

 

  • Go to the IBM Fix Central https://www-945.ibm.com/support/fixcentral/systemx/selectFixes?parent=System%20x3550%20M4&product=ib...
  • Click on IMM2 and download the latest Integrated Management Module 2 (IMM2) Update  …..ibm_fw_imm2_1aoo86d-7.00_anyos_noarch
    1. The file should be ibm_fw_imm2_1aoo86d-7.00_anyos_noarch.uxz (73.17 MB)
    2. Extract the .UXZ and copy the file imm2_1aoo86d-7.00.upd to the Update folder.
  • Click on the UEFI and download ….IBM uEFI Flash Update  ibm_fw_uefi_d7e166d-2.80_anyos_32-64
    1. The file should be ibm_fw_uefi_d7e164c-2.70_anyos_32-64.uxz (3.65 MB)
    2. Extract the .UXZ file and copy the file ibm_fw_uefi_d7e166d-2.80_anyos_32-64.upd to the Update folder.

 

You will also need to download the following utilities.

 

  • Download the Advanced Settings Utility from https://datacentersupport.lenovo.com/us/en/documents/lnvo-asu
    1. The file should be called lnvgy_utl_asu_asut94o-10.5_windows_x86-64.exe
    2. Copy the .exe to a directory on the hard drive.
    3. Double-click on the .exe or run it from the command line. 
    4. The asu64.exe will be extracted to the local hard disk folder.
    5. Copy the file asu64.exe to the Update folder.

 

 

At this point your update folder should look like the following.

foldercontent.png 

 

Open a command line. Please be sure to run as administrator.

 

Browse to the Update folder.

 

You will need to use your own environment’s IP and passwords, and have a network connection to the IMM.

 

Please run the following commands:

Flash IMM 7.00 1aoo86d, Reset IMM

  • exe --host <IMM IP Address> --user <IMM USER NAME> --password <IMM PASSWORD>  --package imm2_1aoo86d-7.00.upd --bypass_platform --skip_min_level --force --no-reboot
  • exe rebootimm --host <IMM IP Address> --user <IMM USER NAME>  --password <IMM PASSWORD>  

Example:

1)    iflash64.exe --host 192.168.70.125 --user USERID --password PASSW0RD --package imm2_1aoo86d-7.00.upd --bypass_platform --skip_min_level --force --no-reboot

2)    asu64.exe rebootimm --host 192.168.70.125 --user USERID --password PASSW0RD

 

Flash UEFI 2.80 d7e166d primary, power on

  • ipmitool -l lanp -H <IMM IP Address> -U <IMM USER NAME> -P <IMM PASSWORD>  chassis power off
  • exe --host <IMM IP Address> --user <IMM USER NAME>   --password <IMM PASSWORD>  --package ibm_fw_uefi_d7e166d-2.80_anyos_32-64.upd --bypass_platform --skip_min_level --force --no-reboot
  • ipmitool -l lanp -H <IMM IP Address> -U <IMM USER NAME>   -P <IMM PASSWORD>   chassis power on
  • After power on the system will reboot several times to install the updated UEFI. Do not power off the system until this completes.

Example

  • ipmitool -l lanp -H 192.168.70.125 -U USERID -P PASSW0RD chassis power off
  • exe --host 192.168.70.125 --user USERID --password PASSW0RD --package ibm_fw_uefi_d7e166d-2.80_anyos_32-64.upd --bypass_platform --skip_min_level --force --no-reboot
  • ipmitool -l lanp -H 192.168.70.125 -U USERID -P PASSW0RD chassis power on

 

 

Check out current deals!


Shop current deals

ALERT

Windows 2016 Server November Update
Issue on System x M5 and X6
Go to details
.

Top Kudoed Authors