OmniStack 5.1.0U1 is now available

[Kipp_Glover]

Today OmniStack 5.1.0U1 was released for SimpliVity!!

This is the full GA release for existing (Gen10, Gen10+) customers to update to 5.1.0 U1 and introducing SimpliVity Gen11 for general availability.  

With this release, the following items are now available for download:

• SimpliVity OmniStack 5.1.0U1 Software
• SimpliVity OmniStack Firmware Bundle - SVTSPGen11-2024_0830
• SimpliVity OmniStack Interoperability Guide 5.1.0U1
• SimpliVity OmniStack 5.1.0U1 Release Notes

Please reference the Customer Notice announcing this 5.1.0U1 release. 

[Marcel_I]

Hi Kipp,

There were multiple upgrade issues when upgrading to OmniStack version 5.0.0.

- https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00138760en_us
- https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00139083en_us
- https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00142165en_us
- https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00142117en_us

Do we still need to implement those workarounds when we are going to upgrade from 4.2.0 to 5.1.0U1? Or are all those issues solved when upgrading direclty to 5.1.0U1?

Thanks.

[Kipp_Glover]

Good day Marcel_l

The three upgrade issues you have linked are resolved in 5.1.0U1.   You do not need to implement the workaround before upgrading to 5.1.0U1.  

Cheers!
/Kipp

[Marcel_I]

Hi Kipp,

Perfect, thanks!

And what about the issue in the last link? 
Advisory: HPE SimpliVity - LUN_RESET smartpqi Error May Cause SCSI Aborts on SimpliVity OmniStack 5.0.0

Kind regards,

Marcel

[Kipp_Glover]

Hi Marcel,

Yes, the LUN RESET issue is resolved with 5.1.0U1.   Sorry, I should have mentioned that as well.  

Cheers!
/Kipp

[Marcel_I]

Thanks Kipp!

[Convergo]

Based on the release notes I found there is a known issue in upgrading the MVA. We are now on 5.0, before upgrading tot 5.1.0U1 the MVA is being upgraded.

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00004278en_us&page=GUID-2CD80F05-D8DF-4466-B456-234D632FA29D.html&docLocale=en_US

Having started the upgrade in a 5.0 federation, the MVA in our main cluster is getting deleted as described in the known issue. We are unable to redeploy it while the upgrade manager copied the new iso to /mva/deploy on all SimpliVity 5.0 nodes in this specific cluster. When deploy a MVA via the upgraded SimpliVity plugin it expects the 5.0.0 binaries in the /mva/deploy location, and has some troubles with the old IP address assigned to the destroyed MVA.

For now we raised a case for support to fix this issue, but be aware this could be a showstopper when planning and executing an upgrade of your federation

[Kipp_Glover]

Good day Convergo,

The issue you refer to, OMNI-112282, will be fixed in the next release (post 5.1.0u1) of OmniStack.  

/Kipp