iSCSI Portal Listening on VIP Address
Description
Problem/Justification
Impact
Activity
Bug Clerk October 22, 2024 at 12:10 AM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Tony Bowers October 21, 2024 at 10:09 PM
If iSCSI ALUA is selected, it will disable the VIP address from listening.
No further investigation needs to be done. I was able to get my answer. This can be closed
Bug Clerk October 21, 2024 at 10:00 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
I have a iXsystems X20 with dual controllers. I have recently tried diving into iSCSI and found a bug with the iSCSI portal listening on VIP addresses when 0.0.0.0 is not selected. The listed IP addresses are for the interfaces on controller A and controller B. VIP address is not listed.
When I go to the drop-down menu under “IP Address”, the options I have are
If I select “192.168.2.1/192.168.2.2” and remove “0.0.0.0”, the controllers stop listening on the VIP address. This is further confirmed by connecting via SSH and showing the services that are listening on port 3260.
If “0.0.0.0” is selected, the iSCSI service shows listening on *:3260. If “192.168.2.1/192.168.2.2” is selected, the iSCSI service shows listening on 192.168.2.1:3260 on controller A and 192.168.2.2:3260 on controller B . This renders the VIP address useless for iSCSI and there is no other way to filter/select the addresses for iSCSI to listen on.
Very simple fix: include the VIP address in the iSCSI portal IP addresses. The HA protocol is based very similar to the VRRP protocol. The active controller just needs to start listening on both IP addresses (VIP and configured)