Really, Netapp, there are Things for improvement. As example: how do you communicate with customers if you shutdown node Base licenses and Provid no support from 01.01.25. If customer did not convert to capacity based license? In Our case no communication and this not the first Time happened. Another great example was the blue xp support for red hat 7.7. The first day after end of support - we had no info, the containerupdate on the connector crashed, the license was not extended and 14 days later shutdown of the ha. (Not one error / info in Blue XP and no support for connectpr because EOL. So informing us was competly missed several times. Thank good, Someone implemented in blue XP a Warning. I thought years about this never used warning and did sometimes Bad jokes about it.
Then netapp Provide a very unclear Dokumentation, forgot Several edge cases and if you ask you get from 3 persons 3 fully divergating Infos. Wanna some Exemples? The wording iswrong, we think it Affekt only BYOL another info: also with node Based license you get support until 2026 or 2027. Another: support ends with node Based license on 31.12.
Next: the license covert Tool in bluexp. If you trust them, you can try it as stated in docu, and if you got get the answer that in your case requirments are fullfilled and then you run in a Bug, the node get New seriell, your Cloudlicense is invalid and your Old by node licenses are deleted. Maybe also a way, that a customer MUST switch, if not, after 1 day because of the now invalid license in Ontap with expiration today you get a shutdown on midnight
And last but not least: Kb article Shows the wrg pic
Netapp: Serious 14 days before Christmas to bring such jokes to your customers. Do you try to go the Citrix and Oracleway?. Make licenses expensive that nobody wanna bu5y it? Or do you hate your customers? You can hate me for beeing sarcastic - Implementing half ready changes, where you got 100% the fun to run in a Bug and Whats next?