iSCSI connection to two portal groups - Only one IP listening

[cstamato]

Hello to all,

I am new to the product, so bare a little with me :)

I've got FreeNAS (latest version) installed on a box with two physical NIC in different subnets, 172.16.55.99/24 and 172.16.56.99/24.
For the moment I use the first interface only for management.
I want to setup iSCSI to create a storage for an virtualization box.

I follow the guides step by step.
I create (for test) two iSCSI prortal groups on both IPs.
The problem that on the first subnet, I can normally connect with iSCSI initiator to FreeNAS box and I can see the drives.
But I can't connect on the second subnet. I always get timeout from the devices.

I ssh to the box.
With netstat -an | grep 3260 I notice that the box is listening only on 172.16.55.99 and not on 172.16.56.99. I am assuming this is the reason I can't connect. FreeNAS is not listening on 172.16.56.99.
I checked also /etc/ctl.conf (think is the name, dont have the box in front of me) and I can see both IP on this file.

What am I missing?

Thank you in advance for your help.
:)

 

[Artion]

Have you tried adding portal IPs?

 

[cstamato]

Hello Artion,

Thank you for you answer.
As I mentioned of my first post, I have created two portals: 172.16.99.50:3260 and 172.16.100.50:3260
My iSCSI initiator IP is 172.16.99.3. All traffic as allowed between the two subnets.

From 172.16.99.3 I can normally ping 172.16.100.50.
From the initiator when I connect to 172.16.99.50:3260 connections is successful.
When I connect to 172.16.100.50:3260 the connection is unsuccessful.

The box is only listening to only one IP 172.16.99.50. It doesn't listen on 172.16.100.50:3260

I really struggled today to get it up working with no luck.
Purpose is to seperate iSCSI traffic using a different subnet.

Any ideas on it? Box should listen on the second IP also, correct?

Thanks in advance

 

[bigphil]

Post a screenshot of your network interfaces config from the FreeNAS box. Also post a screenshot of your iSCSI target config on FreeNAS so we can make sure iSCSI groups are setup correctly. I assume you're trying to create shared storage for multiple virtualization hosts?

*EDIT: I can actually see from your ctl.conf file that the issue seems to be that you have not associated portal group 1 (pg1) with the target so the initiator from 172.16.100.x has no target to connect to. If you want shared storage (multiple initiator access for a clustered file system), simply add another iSCSI group to this target or create a new target and associate portal group 1 (pg1) with it for non-shared storage.

 

[cstamato]

Hello,

I am providing the information. I have made some rearrangements on the portal and targets but still no luck. 2 portals, 2 targets, 1 to 1 target association.
Now the box is listening on both IPs normally.
I tried also to create one portal with both IPs but behavior is still the same.

I can connect to the target of 172.16.99.50 portal and can't connect on the target of 172.16.100.50 portal

What do you think?

 

[bigphil]

Post a screenshot of the initiators from the FreeNAS interface. The way you have it setup, you'll need both initiator names in group 1.

 

[cstamato]

On the initiators there is only one group, id 1, ALL/ALL. I am allowing everything.
By initiator names you mean initiator subnets?

 

[bigphil]

In post #3 you say your initiator IP is 172.16.99.3. Do you only have one initiator and not two? If so, that's not how this works. You'd need a separate initiator IP on the 172.16.100.x network.

 

[cstamato]

Hello bigphil,

First of all, thank for your answers.
Let me make is simpler:
Initiator: 172.16.99.3
On portal group:172.16.100.50:3260
Routing between VLANs 99 and 100 established.
One target associated to the portal group
Initiators: ALL - ALL
One extent associated to the target.

You are saying that for this setup to work I need an initiator on the VLAN 100?
Even if there is routing established between the VLANs?