SOLVED iSCSI unable to add extra iSCSI group to target (ESX)

[Ken Harvey]

Version: FreeNAS-11.2-BETA2
lagg0: 10.10.250.10/24 (Switch 1)
lagg1: 10.10.251.10/24 (Switch 2)
Initiator 1: 10.10.250.0/24
Initiator 2: 10.10.251.0/24
Portal 1: 10.10.250.10:3260
Portal 2: 10.10.251.10:3260
Target 1: s01t01
Target 2: s01t02
Target 3: s01t03
Problem: I am unable to add a second iSCSI initiator to any target.

I have two ESXi servers that I am trying to connect to my FreeNAS through 2 different switches on different VLAN's and networks.
I am able to connect the first ESX server to all of the targets and LUNs without issue. But I am unable to connect my second ESX server.

The problem that I have is when I try and "Add Extra ISCSI Group" to my one of my targets it does not add, it replaces it. Because of this I have no way of connecting ESX2 to to a a target / LUN because initiator 2 is cannot be attached to a target.

Code:

Steps:
1. Edit target s01t03
	

		
			
		

		
	


		
		
	

	

	

		
			
		

		
	

	a. Portal Group ID is already set to 1
	b. Initiator Group ID is already set to 1
2. Click Add Extra ISCSI Group
	

		
			
		

		
	



	

		
			
		

		
	

3. Select Portal Group ID 2
4. Select Initiator Group ID 2
5. Save

Then when I go in back in to edit s01t03, there is only one Portal Group (2) and one Initiator Group (2). This happens on all of my targets.

Is there another way for me to add another Portal and Initiator Group to a target? Is this just a bug in the web interface?

I have tested this on Windows in Firefox and Chrome, along with Linux in Firefox and Chrome.

 

[kdragon75]

You can add multiple subnets to a group and use a single group. Please file bug report.
As for adding multiple initiators, use the following: "10.10.250.0/24 10.10.251.0/24"
The new UI if unreadable, poorly thought out and horribly buggy.

 

[Ken Harvey]

You can add multiple subnets to a group and use a single group. Please file bug report.
As for adding multiple initiators, use the following: "10.10.250.0/24 10.10.251.0/24"
The new UI if unreadable, poorly thought out and horribly buggy.

I had to wait for another outage window so that I could attempt this. I was a little paranoid to make changes, as every time I changed the Target it would take my SAN offline for my ESX host.

Anyways, thank you for the advice, that actually solved my problem. I eliminated my extra portal and initiator. So now I have one portal with both IP's and one initiator with both IP's. I actually did not know that I could build an initiator with 2 subnets, so thanks for that.

I will also try and submit a bug report for the GUI problem as well.

 

[GEOptic]

Good day Gentlemen!!

Ken, did you created 2 users with the same group ID in Authorized Access? Are you using CHAP ?

Just tried this a it works! (1 portal, target configured with grp 1, but no vlan)

11.1u5 (on ixSystems / SuperMicro 2u)
ESXi 6.7 u1 and 6.5 u2 (on Dell PowerEdge - R730xd - R710)
10Gb nics (no switch/direct connection)

Tks​

 

[Ken Harvey]

Nope, I have not setup CHAP or iSCSI authentication on the SAN. My main reason for this is I have a physical disconnect between the networks.
The only ways to connect to the SAN are either to physically access it, or change the network configuration on the ESX host. In both those cases, I have bigger problems.