Your network contains 20 iSCSI storage appliances that will provide storage for 50 Hyper-V hosts
running Windows Server 2012 R2.
You need to configure the storage for the Hyper-V hosts. The solution must minimize administrative
effort.
What should you do first?
A.
Install the iSCSI Target Server role service and configure iSCSI targets.
B.
Install the iSNS Server service feature and create a Discovery Domain.
C.
Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties.
D.
Install the Multipath I/O (MPIO) feature and configure the MPIO Properties.
Explanation:
Windows Server 2012 includes an iSCSI Target role that, along with Failover Clustering, allows it to
become a cost-effective and highly-available iSCSI Storage Array.
We can connect from our Hyper-V host to the iSCSI target on the storage array with the following
PowerShell command line:
New-IscsiTargetPortal –TargetPortalAddress <IP_Address or FQDN of storage array>
$target = Get-IscsiTarget
Connect-IscsiTarget –NodeAddress $target.NodeAddress
Incorrect:
Not B. Discovery Domains in an iSCSI fabric, like zones in a Fibre Channel fabric, enable you to
partition the storage resources in your storage area network (SAN). By creating and managing
Discovery Domains, you can control the iSCSI targets that each iSCSI initiator can see and log on to.Configure iSCSI Target Server Role on Windows Server 2012
too much arguments in previous versions… It’s asking what to do FIRST so I would go with starting the service – C (This is what I go with, you can search yourself)
0
0
The problem is there are two right answers here. If you’re creating the iSCSI target using MS iSCSI Initiator Service, the you of course need to start it first. The problem is you can ALSO accomplish this using the iSCSI Target Server ROLE. And here comes the “gotcha”
Our best friend, the “least administrative effort.” Why go through the trouble of all that configuration when you can just install the Target Server role and set it up in seconds from there?
Long story short? Go with A. “Least Administrative Effort”
https://technet.microsoft.com/en-us/library/cc772367(v=ws.11).aspx
0
0
C – You need to configure the Hyper-V hosts that run Windows Server 2012 R2. The Hyper-V hosts are the iSCSI Initiators and the storage appliances are the iSCSI targets.
You need the iSCSI Initiator installed first to configure the iSNS server in iSCSI Initiator tool.
0
0
Could be B – Not sure anymore, not well written question. You need to configure “the storage for hyper-v hosts”, does it mean which part of the storage? the iSCSI target or initiator? the iSNS will improve the discover of the 20 targets for the hyper-v hosts, it can be installed first, in any server I believe.
0
0
If you arent sure then why are you posting?
Look,i read all the different opinions on this question,some say the initiators first,others say the targets first,some say the isns then the rest,it says YOU NEED TO configure the STORAGE,so CONFIGURE THE STORAGE first,which is the targets,the explanation also sticks to it,the storage is the targets,the client is the hyperv hosts,why would you configure the clients for storage before the storage itself?
0
0
Best answer here would be : B –
Install the iSNS Server service feature and create a Discovery Domain.
Why?!
Because Least Administrative Effort.
We need to add 20 IScsi Targets to 50 IScsi Initiators (Hyper-v hosts)
Copy-Pasting 20 IQNs to 50 hosts is NOT least Administrative effort.
Installing and Configuring ISNS and configuring the Hyper-V hosts to look at the ISNS server is less work.
So I would g for B : Install and Config ISNS
0
0
It’s B. You don’t need to start the MS initiator service. It’s optional. When you setup the iSNS targets you can point to the initiator then.
http://thesolving.com/storage/how-to-install-and-configure-a-isns-server-on-windows-2012-r2/
0
0