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
I would say B to minimize administrative effort. Installing all of those iSCSI devices on that many Hyper-V hosts would be CRAZY!
0
0
Agree with Blazz
also an iSCSI appliance will already be presenting the drives as it will have its own target built in.
0
0
A is completely wrong
iSCSI Target Server role allows server to become a cost-effective and highly-available iSCSI Storage Array. You have 20 storage appliances already
B is the next step not the first one
C is correct
Microsoft iSCSI Initiator Service should be running on all servers then you can ( B ) set up ISNS to discover and connect targets and initiators.
1
0
I think i have to agree with C
https://technet.microsoft.com/en-gb/library/gg610696.aspx
If you are using an iSCSI SAN, make sure that the Microsoft iSCSI Initiator Service on each host is started and set to Automatic. This topic includes a procedure to ensure that iSCSI portals have been added and that the iSCSI initiator is logged into the array.
1
0
Before you can begin to configure shared storage, you need to start Microsoft iSCSI Initiator service and set it to start automatically in the future.
Exam-Ref. 70-412 ,128 CHAPTER 2 Configure file and storage solutions
0
0
C is correct. The service has to be running (not running by default) on all Hyper-V hosts before you can connect to iSCSI targets.
1
0
C is correct. Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties. it assumes you have already creatd teh iscsi vhd and targer and allowed initiators access to the target. you have to now point hte initiator to the target. on target tab of initiator tool on remote server – type ip address of target and then click quick connnect. target should be discovered.
0
0
netadmin rocked it
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
Question: What should you do first?
I think you still need to install iSCSI Target Server Role service and configure iSCSI targets first. Exam-Ref. 70-412 ,127-129 CHAPTER 2 Configure file and storage solutions. The steps:
1. Installing the iSCSI Taget Server
An iSCSI Target Server can include one or more targets (20 storage appliances). In Windows Server, an iSCSI target is the software interface between a defined set of local iSCSI virtual disks and defined set of remote iSCSI initiators allowed to use those disks. Every iSCSI target on a server must have a unique name such as “Target1″…”Target20”.
After you install the iSCSI Target Server component on the storage server
2.Enabling the Microsoft iSCSI Initiator service on the remote server
You are ready to configure iSCSI storage (share storage).
You still need iSCSI target and iSCSI initiator enable before configure iSNS server service feature.
0
0
iSCSI target and iSCSI initator need to register with iSNS server after install iSNS server service.
You can also use the management application of each iSCSI initiator to add the iSNS server information. For example, if you are using the Microsoft iSCSI Initiator, you can use iSCSI Initiator in Control Panel to add the iSNS server information (on the Discovery tab). (Question Here: Do you need to enable iSCSI initiator?)
Use iSCSI trget server and iSCSI initator might work when you have only a small number of targets, but in a large network, it’s much more manageable if you can find targets automatically. iSNS server acts as a central repository of iSCSI components that are available on a network.
iSNS server is make senes for 20 storage appliances (20 Targets).
My answer is B) Install the iSNS Server service feature and create a Discovery Domain.Sorry for the confusing. And then enable iSCSI Initiator.
Sorry for the confusing.
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
1
The answer is definitely -> C
iSNS is a DHCP Server for iSCSI, like a ipv4 DHCP Server. So a DHCP Server needs clients who will initiate the connection.
Go and configure the iSNS role and the initiators and see for yourself. If you install the iSNS Server role first, and open the iSNS Console, you won’t see any initiators! Why? Because the initiator service is not activated! How should they connect to the iSNS Server automatically? Sure, you can install the role first but the work is not done. First, the initiator service needs to be activated on each server! Then you can manage that initiator with the iSNS service.
It’s like you install a ipv4 DHCP Server, but the DHCP Service on the Windows clients is deactivated.
0
0
The first steps is C:
-> Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties.
0
0