Cannot connect to ISCSI target Server

Simon ETOUNDI 0 Reputation points
2024-04-18T09:05:07.7733333+00:00

User's image

Hello dear all,

I have this issues when i'm trying to connect this to iSCSI initiators (sea-svr1 & sea-svr2) to my target server (sea-dc1).

First of all, i had installed Failover clustering into my two initiators, then installed the FS-ISCSITarget-server role to sea-dc1 and connect the two initiators to them.

Until here, everything has worked, but when i trying to connect sea-svr1 & sea-svr2 to the iSCSI target using this powershell cmdlet : "Connect-iSCSITarget -NodeAddress iqn.1991-05.com.microsoft:sea-dc1-iSCSI-L03-target" i receive the error codes shown in this image.

Does anyone helps me ?


Connect-iSCSITarget -NodeAddress iqn.1991-05.com.microsoft:sea-dc1-iSCSI-L03-target


Connect-iSCSITarget -NodeAddress iqn.1991-05.com.microsoft:sea-dc1-iSCSI-L03-target
Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,464 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
958 questions
Windows Server PowerShell
Windows Server PowerShell
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.PowerShell: A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
5,377 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian Xue (Shanghai Wicresoft Co., Ltd.) 29,891 Reputation points Microsoft Vendor
    2024-04-19T03:54:06.3166667+00:00

    Hi Simon ETOUNDI,

    Thank you for posting in the Q&A forum.

    Please run Get-IscsiTarget on the iSCSI initiator servers and see if it gets your iSCSI target. If not, run Update-IscsiTarget to refresh the information about iSCSI targets and then try Get-IscsiTarget again.

    Additionally, run Get-IscsiServerTarget on the iSCSI target server and make sure your iSCSI target is listed.

    Best Regards,

    Ian Xue

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments
  2. Alex Bykovskyi 1,756 Reputation points
    2024-04-22T06:54:02.6166667+00:00

    Hey,

    Have you create iSCSI target on your target server? You need to create iSCSI target before connecting to the server/portal. https://computingforgeeks.com/install-and-configure-iscsi-target-on-windows-server/

    If the target was created, you can try discovering targets via IP for troubleshooting. Might help:

    https://computingforgeeks.com/install-and-configure-iscsi-target-on-windows-server/

    As another option, you can use StarWind VSAN to create iSCSI target and connect it to your hosts.
    https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/

    Cheers,

    Alex Bykovskyi

    StarWind Software

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    0 comments