You have a server named LON-DC1 that runs Windows Server 2012 R2.
An iSCSI virtual disk named VirtuahSCSIl.vhd exists on LON-DC1 as shown in the exhibit. (Click the
Exhibit button.)
Youcreate a new iSCSI virtual disk named VirtualiSCSI2.vhd by using the existing itgt iSCSI target.
VirtualiSCSIl.vhd is removed from LON-DC1.
Youneed to assign VirtualiSCSI2.vhd a logical unit value of 0.
What should you do?
A.
Run the Set-IscsiVirtualDisk cmdlet and specify the -DevicePath parameter.
B.
Run the iscsicpl command and specify the virtualdisklun parameter.
C.
Modify the properties of the itgt ISCSI target.
D.
Run the Set-VirtualDisk cmdlet and specify the -Uniqueld parameter.
Explanation:
Set-VirtualDisk
Modifies the attributes of an existing virtual disk.
Applies To:Windows Server 2012 R2
-UniqueId<String>
Specifies an ID used to uniquely identify a Disk object in the system. The ID persists through
restarts.
Note: Logical unit numbers (LUNs) created on an iSCSI disk storage subsystem are not directly
assigned to a server. For iSCSI, LUNs are assigned to logical entities called targets.
Incorrect:
Not A: Set-IscsiVirtualDisk
Modifies the settings for the specified iSCSI virtual disk.
-Path<String> (alias: DevicePath)
Specifies the path of the virtual hard disk (VHD) file that is associated with the iSCSI virtual disk.
Filter the iSCSI Virtual Disk object using this parameter.Not B: iscsicpl.exe could is the Microsoft
iSCSI Initiator Configuration Tool. Microsoft Internet iSCSI Initiator enables you to connect a host
computer that is running Windows 7 or Windows Server 2008 R2 to an external iSCSI-based storage
array through an Ethernet network adapter.
Anc: C
0
0
Sakibur. If you think the given answer is incorrect, can you please explain why it is incorrect and why your answer is correct.
This way we can all learn.
Thnx
3
0
The given answer is INCORRECT.
If the LUN that you want to assign is on an iSCSI subsystem, this LUN must be assigned to an iSCSI target. A server or cluster will only have access to that LUN after the iSCSI initiator on that server or cluster logs on to the iSCSI target. For information about iSCSI targets, see Manage iSCSI Targets.
It is the Iscsi Target that presents the storage to the iSCSI Initiator as the configured LUN.
0
0
Check previous questions. Answer is C
0
0
None of them, must be something wrong with the dump. Only the virtual disk properties in the Server Manager gui can do it afaik.
A. Run the Set-IscsiVirtualDisk cmdlet and specify the -DevicePath parameter.
Set-IscsiVirtualDisk doesn’t have an option for the LUN Id, and Get-IscsiVirtualDisk can’t retrieve the LUN Id.
B. Run the iscsicpl command and specify the virtualdisklun parameter.
This is client side and has no facility to change the LUN Id presented by the server
C. Modify the properties of the itgt ISCSI target.
Doesn’t have any way to change the LUN Ids of the virtual disks
D. Run the Set-VirtualDisk cmdlet and specify the -Uniqueld parameter.
Get-VirtualDisk doesn’t have an option for the LUN Id, and Get-VirtualDisk doesn’t return any objects at all for me, whereas Get-IscsiVirtualDisk does at least return my iscsi luns minus the LUN Id
1
0
sorry I meant “SET-VirtualDisk doesn’t have an option for the LUN Id”
0
0
I’m going with Answer: C
Server Manager\File and Storage Services\iSCSI\ Properties of the iSCSI Virtual Disk (aka itgt ISCSI target using older Windows generation wording)
The alternative is not listed: Add-IscsiVirtualDiskTargetMapping
0
0
I’m also guessing the wrong picture is used in the question, as it has no bearing on the question. The picture should show the upper portion of the window displaying iSCSI Virtual Disks.
0
0