38. Connecting to the iSCSI target using MPIO in Windows Server 2019
HTML-код
- Опубликовано: 13 сен 2024
- Video Series on Advance Networking with Windows Server 2019:
In this video guide, We will see the steps on how to use the Windows Server iSCSI Initiator to create a fault-tolerant connection to an iSCSI target by configuring Multipath IO.
1: Install and Configure iSCSI target server role.
2: Install and Configure Multipath I/O on iSCSI initiator server.
3: Configure iSCSI initiator to connect iSCSI storage using Multipath IO.
Configuring iSCSI Storage and Initiator in Windows Server 2019:
• 37. Configuring iSCSI ...
Follow my blogs:
msftwebcast.com
Brilliant, the Lab Setup diagram was really important to show how the servers are connected. Thank you!
A well paced and documented walk through. Enabling MPIO (after installing the feature) has been overlooked in other videos, but you made sure to point it out as an extra step. MPIO was missing as an option to me on mapped LUNs until I spotted that step in your video. Big help.
I also wanted to point out that you may see a MPIO policy other than Round Robin. I have a Quantum QXS SAN with two controllers and my MPIO policy cannot be Round Robin. It's Round Robin With Subset. This stumped me for a bit so I'm sharing. Only one controller owns a LUN at any give time on that SAN so paths can not be active/active to both controllers. Some paths are active/unoptimized. This is called Asymmetric Active Active and you can read more about it here (a vmware article, but good explanation): www.yellow-bricks.com/2009/09/29/whats-that-alua-exactly/
@@jeremyyoung627 Thank You jeremy for sharing such information...Even I learned something new from you...
Well explained so everyone can follow it. Managing several wiindows on one screen might confuse some users, but the tag idea on the top right, clearly guide the follower to make sure you are in the right server, additionally the ppt diagram depicts the idea even more clear. A lot efforts on your end, but is how should be done.
Thank you for all posting all these videos.
Very helpful. Thank you.
perfect
very nice video bro keep it up
Great job. Lets hit 50k.
Thanks for this!! A very vlear and concise tutorial
Thank you David!
Curious, at 1:58, you remove the checkbox for Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and then under IPv4 properties, disable some other things. Sure, you don't need them for an iSCSI only network. But, is there any other reason we *should* be doing this besides the fact they're just not needed? I'm only curious because I've never seen this as a step in configuring iSCSI before.
No other reason do to so. Just to improve performance. But frankly, now even I am wondering is it necessary at all? Need to test more.
The point is to reduce any unnecessary traffic from your iSCSI network/VLAN. Windows server interfaces with all clients enabled broadcast packets on a subnet, and none of that traffic is valid for your iSCSI subnet, so you disable to reduce as much as you can.
Perfect!!!
hi i got error authorize failure when try to connect. any idea?
My question is can the Windows iSCSI target bet used in a Windows cluster environment? Do you need to enable something on the iSCSI target to allow multiple read/write from different sources or is that only handled on the cluster side? So if I want to Cluster Hyper-V.
Hello, Can u please help me in creating a diskless environment/Setup using Windows Server 2019 for Windows 10 VHDX image for diskless clients?
Hi, how to get 3par storage LUN ID's in windows server 2019 VM. Please help us
Hi, If you have two servers, and each server has 4 ports going to ISCSI Target(Dell SAN) Do each of these port need to be on a different Subnet? The Dell Host has SPA and SPB with 4 ports total.
Thank you
Great video, quick question. I assume that you can also use either of the 192 ip addresses for target portal discovery. you dont necessary need to use the 172 IP, right ?
Yes you can!
Was not able to get this to work, MPIO would not connect twice.
The reasons why is I configured the virtual MS server to use the same port networks I set up for the VMware hosts to use for iSCSI MPIO. When configuring MPIO in VMware you need to make one port active, while the other one is unused. This is how its configure din VMware.
The problem is VMs mapped to these port networks will only see one interface up, as the other one is unused. You cant use the same port networks that the VMware hosts uses to set up MPIO on a VM. You would need to connect and configure two NEW interfaces.
Nice Video.
My question is, if connecting more than one initiator server to the target server (storage), will this corrupt the volume on the Storage location?
for example, if i use Windows server hypervisor role on a 2 server cluster and point to the same iscsi target from the 2 servers to the same storage node and volume (cluster storage) for load balancing and live migration, can this corrupt the location?
No. It will not corrupt the volume.
Do I need MPIO if my initiator has only one iSCSI IP while the target has four?
Hello sir. Show us a demo how to disable a user administrator after joining a domain controller.
You mean on client computer using group policy?
@@MSFTWebCast yes sir
@@SuperChelseaSW6 Coming soon.
ok