We are seeing the following error on our Windwos Server 2012 box when connecting an iscsi conenction to the server "Out of Resource" and seeing the following event in the event viewer "The initiator could not allocate resources for an iSCSI connection"
I thought it might be hitting our storage pool limit but we are nowhere near it yet. We have 3 x PS6510X in a single storage pool with 680 conection to it. our maximum for this pool is just over 1000 according to san hq.
Anyone offer any guidance or experienced this at all?
If this is event ID 6: , then from the MS iSCSI Initiator guide here is the description:
The initiator could not allocate resources for an iSCSI connection
This event is logged when the initiator could not allocate resources such as memory, work item, etc. for an iSCSI connection. This can typically happen in low memory conditions
Yes, that's what I mean. 128 sounds deliberate. Are you using HW iSCSI offloading and that maxes out at 128 connections? Broadcom cards let you configure a maximum number of offloaded iSCSI connections in BACS, if I remember correctly.
We have our broadcom 10gb using NPAR. 1 iscis parttion on each phisical port. Its maximum iscsi is set to 64 not 128? surely it can do more than that? lets me change it but wondering what effect this will have ?
This is a windows server not an esx host. We are using it for our Veeam Backups using direct SAN access mode. So we should be allowed a total of 126 session/targets per Port on the card? we only have 20 initiator volumes attached so far but with the MPIO module on there as well its 128 sessions total. If its 126 poer port then we should be allowed more.
You mentioned you have 3 EQLs in one pool, that would get you 6 connections per volume with HIT/ME defaults.
So with 20 volumes attached you'd be at 120 connections already, not much room for connecting to snapshots (which may also consume 6 connections each if you use MPIO for snapshots, which is also the default), if the currently attainable maximum is 128 connections.
I'd check the iSCSI HBA first, if you can't get more connections out of it, you might want to switch to the software iSCSI initiator.
Word of warning, though: Back when I tried using Broadcom iSCSI offload, any configuration change to the Broadcom card would reset it, disrupting all iSCSI connections. I have no experience with your cards, it might be different nowadays.
|Just reading the Broadcom FAQ on our 10GB Card and is states the following:
iSCSI Offloads 128 per port (Single Function) 128 per partition (NPAR)– for up to two iSCSI Offload
Protocol enabled partitions
Seeing as our ports are partitioned with 1 iscsi partition on each port and currently set to 64 iscsi offloads in the BACS Suite , i can increase the 64 to 128? Thats how im reading it ?
mirko.schnellba
25 Posts
1436
0
Posted February 17th, 2014 03:00
Are you possibly hitting the host's iSCSI connection limit? 255 was max in 2008R2 and I don't think that changed for 2012.