cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Seniore
Paper Tape
Posts: 2
Registered: ‎07-03-2019
Location: PL
Views: 161
Message 1 of 3

Firmware upgrade via XClarity timeouts

I'm trying to upgrade firmware on x240 nodes.

The first part (IMM,UEFI,DSA) works flawless, yet when moving to the adapaters (FC, NIC) the process fails.

It seems that the server does not boot in time when preparing for maintenance mode.

The IMM reports "The bare metal connection process has been started" in this time the servers boots the Linux based appliance to perform the upgrade.

After exactly 10 minutes a new event is being logged in the IMM "The bare metal update application reports a status of Timeout".

The remote console shows that the server is still booting (it spends a lot of time on "Starting HAL daemon").

After the timeout the server is being powered off and stays off for a long time.

When manually powering on the server boots the normal OS (in this case ESXi).

 

Does anyone know if this 10 minute timeout is changable and if yes where?

 

Lenovo Employee LancelotSun
Lenovo Employee
Posts: 28
Registered: ‎02-19-2017
Location: TW
Views: 86
Message 2 of 3

Re: Firmware upgrade via XClarity timeouts

For FC and NIC firmware updates, are they successful? If there logs or screeshots are helpful for us to check what kind of this problem.

Highlighted
Seniore
Paper Tape
Posts: 2
Registered: ‎07-03-2019
Location: PL
Views: 73
Message 3 of 3

Re: Firmware upgrade via XClarity timeouts

The FC and NIC firmware does not get updated.

XClarity gets stuck at "Maintenance mode" with 1%.

As mentioned earlier the server itself tries to boot the Linux appliance in order to enter maintance mode.

That seems to take too much time and the process timeouts with visible entries in the IMM log:

"The bare metal connection process has been started"

after exactltyl ten minutes:

"The bare metal update application reports a status of Timeout".

After this the server is being powered off by XClarity.

 

Between the start and the timeout the server actually tries to boot the Linux appliance but it seems it takes too much time.

So the main question would be if it's possible the timeout value that is required to enter maintenance mode?

Check out current deals!


Shop current deals