ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

DL360 GEN10 restart

 
SOLVED
Go to solution
NJK-Work
Honored Contributor

DL360 GEN10 restart

I have a DL360 GEN10 that is having this exact problem:

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00050465en_us

The error in the IML is word-for-word per that article.  However, I have already updated the firmware a while ago and it still happens.  The problem happens about randomly once every 2 weeks or so.  Usually in the afternoon.  So it really had to re-produce the problem.  It is a Citrix server, so when it crashes it boots like 30 people off their session.

I opened a ticket with HPE, and they forwarded it on to our reseller.  The reseller said it "looks like an OS" problem and closed the ticket.  I have 7 other servers built from the same image (Windows 2016) with identical hardware and patched the same way that do not have this problem.  So I think it is a HW problem.

Has anyone else seen this problem with a GEN10 and have a suggestion?

Thanks

NK

3 REPLIES 3
AshutoshM
Frequent Advisor
Solution

Re: DL360 GEN10 restart

Hi

If BIOS is already at version 1.42 then you may try setting the workload profile to "High Performance Compute".

System Configuration > BIOS/Platform Configuration (RBSU) > Workload Profile > High Performance Compute

If this fails to resolve then suggest updating the BIOS to the currently available 1.50 version.

https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=1010093150&swItemId=MTX_cd5de2cd63294b9f99a502cf98&swEnvOid=4184#tab-history

 

Note:This issue is not unique to HPE servers.

I am an HPE Employee
NJK-Work
Honored Contributor

Re: DL360 GEN10 restart

Thanks.  I am already at the 1.50 BIOS version, but I will try the High Performance Compute option.

NK

NJK-Work
Honored Contributor

Re: DL360 GEN10 restart

Apologies - just relealized I never commented back to this problem.  The "High Performance Compute" option appears to have worked...I have not had a crash since.  For consistency, I applied to the change to all the Citrix servers (not just the one having the problem).  Does not seem to have an adverse affect on any of them.