- #5.4.8 testout lab configure the iscsi initiator install#
- #5.4.8 testout lab configure the iscsi initiator Patch#
- #5.4.8 testout lab configure the iscsi initiator for windows 10#
- #5.4.8 testout lab configure the iscsi initiator windows 10#
Let us now get onto targetcli admin console to create our target(s) $ sudo su -Ĭopyright 2011-2013 by Datera, Inc and others. Step 5: Configure iSCSI Target on CentOS 8 / RHEL 8Ĭreate a folder in your configured disks for example in /var/ or a mount point for your secondary disk, or a raid device. If you have a secondary disk on the server, I recommend you use it. Tmpfs tmpfs 380M 0 380M 0% /sys/fs/cgroup $ df -hTįilesystem Type Size Used Avail Use% Mounted on It is advisable to set a different partition for this so that it is easier to manage without interfering with the core CentOS files and system. This is to make sure there is enough disk space or blocks available for allocation.
#5.4.8 testout lab configure the iscsi initiator install#
Install it by running the command: sudo dnf -y install targetcli Step 4: Check available space on your system The package for iSCSI Target is available as targetcli on your CentOS 8 / RHEL 8 default AppStream repositories. Step 3: Install targetcli package on CentOS 8 / RHEL 8 who really connect Win10 to a iSCSI target.As this setup covers configuration of SELinux, keep it running in an enforcing mode.
What step is missing? BTW, I don't think it is the firewall setting.Īnyway, I will let it be. I can get it to connect via other mean, but I bug me that a clean setup and it don't work the way I believe it should. I tried giving the Win10 client a fixed IP, but same issue. Maybe it is because the Win10 client is using the router's DHCP to get the IP address while the servers is using fixed IP.
#5.4.8 testout lab configure the iscsi initiator windows 10#
Note: I can select from the "Select from the initiator cache on the target server:" the Windows 10 client IQN to get it to connect. I still can't use the “Query initiator computer for ID" to discover the windows 10 client. (step is type the hostname into the dialog box and click "OK",Įven after I go to the Windows 10 clients, start the initiator then add the iSCSI Target Server IP address, then I go back to the iSCSI target server, I can see the windows 10 IQN appear in "Select from the initiator cache on the target server:". I have no issue adding the other servers as the initiators via the “Query initiator computer for ID", but not for the Windows 10 clients. Note: I have not do anything on the servers or clients (which will connect to this iSCSI Target) yet meaning
but that is not the question.įrom the iSCSI target server, I started the "New iSCSI Virtual Disk Wizard" and from there I can add the other servers as the targets. The "Enter a value for the select type" and use DNS to add the windows 10 clients. I can get it connected by configuring the Win10 initiator by adding the iSCSI target hostname. The question is why do I get this error "Unable to determine." when I enter the correct name or via 'browse' button to get the correct name for Win10, while it work without issue with Win2016 servers.įrom your suggestion, I believe you think that I can't get the Win10 client connected to the ISCSI target server. Sorry, if I've not explained properly in my initial post, or I don't get what you are trying to said.
#5.4.8 testout lab configure the iscsi initiator for windows 10#
Is there extra step I need to take for windows 10 client compared to Windows 2016 server? Can't be the windows 10 "-" in the hostname causing the issue right?
#5.4.8 testout lab configure the iscsi initiator Patch#
Note: this is a clean lab setup with latest patch applied. When I tried again to create another target and using the “Query initiator computer for ID” to add the same Win10 client again, it failed with the same result. Initiator using the cache target IQN, and connect from the Win10 client the iSCSI disk. From the iSCSI server end I can select and add it as the Then from the Win10 client I started the initiator and query the iSCSI server, then the win10 client’s IQN appear in the iSCSI server wizard “Select from the initiator Cache on the target server:”. Hostname via the AD to make sure the name is correct. While using the wizard to add the initiators I have no issue adding the hostname of servers via the “Query initiator computer for ID”, but it failed with Windows 10 with “unable to determine IQN for the client”. From the iSCSI storage server, I create iSCSI targets and add other VMs as initiators. There are 2x DC, 1 iSCSI target and 1 initiator server, and 2 Windows 10 clients VMs, in a single AD (except for the hyper-V host). Hi, I just setup a VMs lab using hyper-v.
0 kommentar(er)
