topic Re: 5.0.0 Advisory on changing the queue depth in HPE SimpliVity

5.0.0 Advisory on changing the queue depth

Kipp_Glover — Mon, 12 Aug 2024 16:10:04 GMT

Good day All!

Anyone running 5.0.0 must read this advisory and apply the change to the queue depth. Not everyone will hit this, but anyone running 5.0.0 has the incorrect queue depth setting. No downtime is needed to apply the change.

The script only does one node. If you want to push the change to your entire federation, then contact support and they can use Zeus to push the change to the entire fed.

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00142117en_us

Re: 5.0.0 Advisory on changing the queue depth

chris_graham — Tue, 13 Aug 2024 17:35:58 GMT

Thanks for the Info. I could have used this last week.

Do you know if there was an email sent out for the advisory?

Re: 5.0.0 Advisory on changing the queue depth

Kipp_Glover — Tue, 13 Aug 2024 18:46:44 GMT

Yes, a Support Alert was sent regarding this issue. If you have a Support Alert subscription to SimpliVity you should have received the alert.

Re: 5.0.0 Advisory on changing the queue depth

chris_graham — Mon, 16 Sep 2024 09:09:27 GMT

Thanks Kipp, It apeears i did not recive the email. I did recieve the july 29th firmware upgrade Alert.

I have had multiple tickets open with support for OVC failures and nobody was aware of this issue with 5.0. It look a full cluster failure on friday to find out it was a queue depth issue. seems like there was a communication breakdown somewhere.

Re: 5.0.0 Advisory on changing the queue depth

Kipp_Glover — Tue, 13 Aug 2024 20:07:53 GMT

Hi Chris,

I'm checking to ensure this wasn't an issue with the Support Alert process. Sorry to hear you experienced a cluster-wide issue on Friday. I will revisit this issue with our support team.

Thanks!
/Kipp

Re: 5.0.0 Advisory on changing the queue depth

Kipp_Glover — Wed, 14 Aug 2024 16:52:55 GMT

There was an issue with stuck SimpliVity Support Alerts. The issue is now resolved and they are flowing again. Thanks Chris for bringing this to our attention. I am sorry you didn't see the advisory earlier to prevent your issue.

/Kipp