Closed TimMcGue closed 1 month ago
@TimMcGue thanks for your feedback. I'll discuss this issue with the team and update the documentation accordingly.
We're asking the vendor for any specific issues with direct upgrade from 3.4.x.x -> latest EFOS version. There is some evidence that the QoS configuration introduced with RCF 1.6+ requires EFOS 3.4.4.6 and later.
@TimMcGue thanks for your feedback. The upgrade process for switch BES-53248 has been updated and is available online here: https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/upgrade-switch-overview.html Closing this issue.
Page URL
https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-efos-software.html
Page title
Install the EFOS software
Summary
Hello doc team,
So currently the great table on this page lays out the requirements for upgrading. Currently if a customer is running 3.7.x.x upgrading to any version looks straight forward (as long as they stay with the FIPS/non-FIPS configuration).
The question comes up for the 3.4.x.x and the 3.4.4.6 entries. I double checked on Broadcom's documentation site for their take and unfortunately their documentation is not quite as tenured as our docs site is so the detail on that requirement just isn't there that I can find. I'm wondering if those particular recommendations (to hop upgrade if at a version prior to 3.4.4.6 and to wipe the switch configuration) are there specifically about the ISL negotiation that changes in the 3.7 releases? With the recent changes that were made to the docs with the no longer requiring the ISL to successfully upgrade as well as the "undo" steps for the RCF, maybe this table can go through another review with engineering to give customers still on those older releases more flexibility to upgrade to the newer EFOS versions without needing hops/wipes.
Public issues must not contain sensitive information