IMM web interface (IBM X3550 m3) [!SOLVED!]

Hi
I just managed to get the web interface to show up on my browser, but I was not able to log into it using the default username and password. It just kept me on the logging in page, and did not provide me with “wrong password/username” promt

Any ideas what could be causing it
This behavior happens both on Chrome and Firefox
Any error codes I should be looking for within the devtools/F12 console?
I don’t have the space heater currently running, so I cannot just copy paste it here.

Edit
I have already resetted the password and username to the defaults twice

I’d try to reset the User/Password.

1 Like

Oh, sorry
I should have mentioned this originally, but I did that twice with this guide

1 Like

What’s your IMM Firmware Version?
IIRC there’s a bug where the webinterface will hang after login in some earlier version.

yeah, I ll add that to this thread
And copy this to the other one
Since I have two indentical units

SVR2 (the more up to date)

Host Firmware (UEFI)
Version 1.08
Build ID D6E148BUS
Build date (AM. 06/25/2010 /Others 25.06.2010)

IMM (integrated management module)
Version 1.48 YU00G8C
Date 14.04.2015

Diagnostics
Ver. 3.10
Build ID DSYT70X
Build date 12.06.2010

SVR1 (more out of date)
This unit currently has 48gb of RAM, and issues with the detection of the IMM. Which leads to relativly long boot time compared to SVR2. And is missing a fan…
Not great, since it too has two CPUs

Host Firmware (UEFI)
Version 1.08
Build ID D6E148BUS
Build date (AM. 06/25/2010 /Others 25.06.2010)

IMM
Ver. 1.14
Build ID YU0073M
Build Date 22.06.2010

Diagnostics
Ver. 3.10
Build ID DSYT70X
Build date 12.06.2010

And I already opened a thread about the firmware update, which is not as easy as one might think, Or I just have totally missed how to use it.

Here are the errors


I cannot honestly make anything out of these, since I am not familiar with JS

Update
This error does not persist, when Using MS IE, since it’s quite old platform
Modern Chromium based browsers are not going to work
So this issue can be worked around