snowmirage
Dabbler
- Joined
- Sep 20, 2011
- Messages
- 29
I have had 2 iSCSI "shares" setup on my FreeNAS box for over a year now and as far as I know everything has been working fine. Today I went to add a third and in the process noticed something that has me confused / baffled.
I have 3 portals setup as follows
Portal Group ID Listen Comment
1 0.0.0.0:3260 desktop-portal
2 0.0.0.0:3261 syslog-portal
3 0.0.0.0:3262 esxi-portal
all of which are associated with different targets and file extents.
#1 and #2 have been working for over a year. When I went to add the 3rd for my esxi server I could not get it to discover a device when I pointed the discovery to port 3262 for the IP of my FreeNAS box. But if I pointed it to port 3260 it discovered a device.
In troubleshooting I noticed that my syslog server and my desktop which both have working iSCSI devices setup appear to both be connecting to the FreeNAS server over port 3260! (verified in tcpdumps)
I fear that both the syslog box and my desktop are some how connected to the same iSCSI file extend. I can't imagine they would be working this whole time if the system would even allow that to happen.
If my syslog box is connecting to the correct extents wouldn't it HAVE to be using port 3261 based on my config? If all iSCSI connection go through one port I don't see how the system differentiates which traffic is for which file extent if you are not using authentication (which I am not I have them all using the same "Initiators" group)
Since its a block layer device I can't just ssh to the FreeNAS box cat out a file or look a directory to make sure each iSCSI client is connecting to the right "share".
Can anyone suggest some way I can verify they are connecting to the right file extents? I can't even go monitor the size of the files on the FreeNAS box since the file extent size is set when its created.
I have 3 portals setup as follows
Portal Group ID Listen Comment
1 0.0.0.0:3260 desktop-portal
2 0.0.0.0:3261 syslog-portal
3 0.0.0.0:3262 esxi-portal
all of which are associated with different targets and file extents.
#1 and #2 have been working for over a year. When I went to add the 3rd for my esxi server I could not get it to discover a device when I pointed the discovery to port 3262 for the IP of my FreeNAS box. But if I pointed it to port 3260 it discovered a device.
In troubleshooting I noticed that my syslog server and my desktop which both have working iSCSI devices setup appear to both be connecting to the FreeNAS server over port 3260! (verified in tcpdumps)
I fear that both the syslog box and my desktop are some how connected to the same iSCSI file extend. I can't imagine they would be working this whole time if the system would even allow that to happen.
If my syslog box is connecting to the correct extents wouldn't it HAVE to be using port 3261 based on my config? If all iSCSI connection go through one port I don't see how the system differentiates which traffic is for which file extent if you are not using authentication (which I am not I have them all using the same "Initiators" group)
Since its a block layer device I can't just ssh to the FreeNAS box cat out a file or look a directory to make sure each iSCSI client is connecting to the right "share".
Can anyone suggest some way I can verify they are connecting to the right file extents? I can't even go monitor the size of the files on the FreeNAS box since the file extent size is set when its created.