I think it would be beneficial for IBM but also for customers if the SVC license for SVC clusters that virtualize IBM Flash systems (FCM) were based on usable capacity and not on offered volumes\Mdisks.
Original Message:
Sent: Thu February 06, 2025 04:56 AM
From: Markus Standau
Subject: IBM SVC License
Actually you have the answer right in front of you:
1) a definition of what is regarded as usable capacity
2) a instruction that you need sufficient SCUs for the usable capacity (again wicht is defined in the very same document)
3) there is no restriction of device vendors
Just note:
- because of that definition and the technical implementation of data reduction in the backend, the SVC license panel will not be able to show you the number of SCUs, because SVC doesn't typically know the usable capacity of the backend
- Since the used capacity is changing with each write, you really should calculate with the usable capacity of the whole backend RAID array, as that's the maximum the mdisks/Luns can grow to. If all the capacity of the RAID array is assigned to one SVC this is simple, but if you share the capacity between SVC and some other servers (i.e. System i) than there is the question, what is the usable capacity of the mdisks, and there is no good answer for this in a mixed scenario, so I would default again to the usable capacity of the complete array, and avoid sharing it with other servers - I hope I could explain this, but if you think it through step by step you get what I mean
------------------------------
Markus Standau
Offering Leader for FlashSystems and SVC
IBM
Walldorf
Original Message:
Sent: Thu February 06, 2025 03:22 AM
From: T Masteen
Subject: IBM SVC License
Ian, Christian,
Thanks for your responses.
Usable Capacity:
When virtualizing backend storage arrays with data reduction technology, "Usable Capacity" is the physical capacity available on the backend storage array before taking into consideration any data reduction.
In the document Christian provided is also stated.
Sufficient entitlements must be obtained for the number of Storage Capacity Units required to cover the TBs of usable capacity managed by the Program as set forth below.
This in relation to the explanation about usable capacity raises questions for me.
But I will take this to sales.
Thanks
------------------------------
TMasteen
Original Message:
Sent: Thu February 06, 2025 02:31 AM
From: Christian Schroeder
Subject: IBM SVC License
Another good source of information on this matter is the SVC License Information at https://www.ibm.com/support/customer/csol/terms/?id=L-UMTT-HF5W9J&lc=en
It basically tells the same as mentioned above by Ian.
According to the information in there, no distinguation is made between back-end storage controllers from IBM or other vendors.
Interesting detail on the Usable capacity, though:
Usable Capacity:
When virtualizing backend storage arrays with data reduction technology, "Usable Capacity" is the physical capacity available on the backend storage array before taking into consideration any data reduction.
I understand it in this way, that for instance the usage of compression or deduplication on the back-end storage would not impact the count of SCU to be licensed. FCMs actual physical capacity compared to their nominal capacity, would not reduce the SCU count, either. That said, eventually it is the back-end storage's sum of LUN capacity presented to SVC as mdisks determines the capacity / SCU to be licensed.
------------------------------
Best regards,
Christian Schroeder
IBM Storage Virtualize Support with Passion
Original Message:
Sent: Wed February 05, 2025 01:29 PM
From: Ian Wright
Subject: IBM SVC License
I wonder if the SVC licensing for non-IBM backend arrays is based on managed disks coming from these arrays, and that the SVC licensing for backend IBM Flashsystems is based on usable capacity of the Flashsystem (so not based on mdisks).
Ok, I see what you're asking. The key to this is that it's based on the Usable TiB, but needs to be converted into Storage Capacity Units. So, there place that I would look is here: Licensed functions - IBM Documentation
But the key is that you need to know the "class" of storage that your working with. It's generally going to fit into the "flash" tier these days, but you might have some times that you're using NL drives or even, rarely, SCM.

Does that make sense?
edit: and just to clarify... According to the latest documentation everything is done by SCUs. Previous version of documentation have indicated licensing enclosure with FlashSystems. So, I think that's no longer an option.
------------------------------
Ian Wright IBM Champion for Storage, Red Hat Accelerator
System Engineer
Mainline Information Systems
Original Message:
Sent: Wed February 05, 2025 12:10 PM
From: T Masteen
Subject: IBM SVC License
I wonder if the SVC licensing for non-IBM backend arrays is based on managed disks coming from these arrays, and that the SVC licensing for backend IBM Flashsystems is based on usable capacity of the Flashsystem (so not based on mdisks).
Thanks.
------------------------------
TMasteen
Original Message:
Sent: Wed February 05, 2025 09:48 AM
From: Ian Wright
Subject: IBM SVC License
What exactly is it that you're wondering?
The software is identical, though the licensing is different since the SVC is based on the amount of capacity (and class) that is being abstracted.
Can you give more detail to your question?
------------------------------
Ian Wright IBM Champion for Storage, Red Hat Accelerator
System Engineer
Mainline Information Systems
Original Message:
Sent: Wed February 05, 2025 05:35 AM
From: T Masteen
Subject: IBM SVC License
Hello Team,
Is there an url where I can find some details about SVC licenses?
Maybe there is no difference between IBM Flashsystems and other vendor arrays as Backend for SVC?
Thank you.
------------------------------
TMasteen
Original Message:
Sent: Fri January 31, 2025 11:28 AM
From: T Masteen
Subject: IBM SVC License
Hi,
From the SVC perspective, does it make a difference in terms of license whether you have an IBM Flash system (with FCMs) as a backend or one from another vendor?
Thanks.
------------------------------
TMasteen
------------------------------