Well, I have tried ISCSI with IBMi in the past, with different scenarios: Storwize V7000 Gen1, Flashsystem V5010, Linux iSCSI TGT server, and also worked with Skytap (now Kyndryl Cloud Uplift).
All my attempts were using 1Gb ethernet with multiple connections, and besides the throughput , we observed high latency, so it is not an option, for me, for production environments.
But...
Skytap has been using ISCSI for years in production environments, because they have their own OpenStack framework and they can get the features they need from iSCSI-based storage devices (like IBM XIV competitors). Not sure if as of today they have moved to FCP, but they have a very tight partnership with Microsoft Azure, and ISCSI-Based cloud, so...
What I have learned is they can provide a very improved and acceptable performance using server-side caching, but still you can notice some issues with IBM i traditional workloads, and makes sense.
A high amount of small requests to your disk backend can kill any storage subsystem when you have high latency, and iSCSI provides more than 2ms with some load.
If we compare actual NVMe storage, internal or external (FC), with any other technology, we are talking about a consistent 0.33 ms latency.
In the past, with mechanical hard drives (15K RPM) and good RAID adapters (1GB cache or even more), we were able to get 1ms ~ 2ms response times (always with the right sizing).
With XIV (sorry, I never liked IBM XIV systems) from latest generations, using internal infiniband and FC to your IBM Power box, you could get worst response times than using a FlashSystem 5100 with IBM I, because of latency. I have seen 4ms to 8ms with XIV...
My recommendations:
- If you want to build an openstack thing, like Skytap/Kyndryl, and have enough resources, you can go on, but you won't have IBM official support.
- If you need small development/test environments, this could be an option
- If you need for production environments, please, don't forget the lack of IBM support.
- If you have high I/O workloads, specially with RPG or Cobol code, try a different thing.
- SQL workloads can get a decent response time, but you need enough resources in your VIOS.
- If you can afford it, use a switch, to have paths from both controllers on each VIOS.
Good luck, and please, let Us know to learn about your case!
------------------------------
Diego E. KESSELMAN
IBM Champion
ESSELWARE Soluciones
------------------------------
Original Message:
Sent: 07/29/26 03:17 PM
From: Brian Bohner
Subject: iSCSI disk inside VIOS assigned to IBM i client LPAR using vscsi
I ran across this thread and providing a follow up - July 29, 2026:
I checked with IBM i development and as Satid indicated, IBM i doesn't support iSCSI attached storage. This was mainly due to performance. They can be presented to VIOS and then use vscsi and hdisks to present to IBM i, but understand the limitations, mainly on performance.
------------------------------
Brian Bohner
IBM i Global Support Center
------------------------------