You have a server named LON-DC1 that runs Windows Server 2012 R2. An iSCSI virtual
disk named VirtualiSCSI1.vhd exists on LON-DC1 as shown in the exhibit. (Click the Exhibit button.)
You create a new iSCSI virtual disk named VirtualiSCSI2.vhd by using the existing itgt iSCSI
target.
VirtualiSCSIl.vhd is removed from LON-DC1.
You need to assign VirtualiSCSI2.vhd a logical unit value of 0.
What should you do?
A.
Modify the properties of the itgt ISCSI target.
B.
Modify the properties of the VirtualiSCSI2.vhd iSCSI virtual disk.
C.
Run the Set-VirtualDisk cmdlet and specify the -Uniqueld parameter.
D.
Run the iscsicli command and specify the reportluns parameter.
Explanation:
The virtual disk has the option to change the lun ID, no other option available in the answers
appear to allow this change.
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.
I think its ‘A’
Wrong, because there is no parameter for change Lun
Answer is B, I tested in virtual lab https://vlabs.holsystems.com/vlabs/technet?eng=VLabs&auth=none&src=microsoft.holsystems.com&altadd=true&labid=10844 🙂
thanks
Thanks Di!
In my lab the syntax below updated the LUN number so, I agree B for the GUI approach
Add-IscsiVirtualDiskTargetMapping -TargetName “TargetOne” -DevicePath “E:\Temp\vhd1.vhdx” -Lun 5
https://technet.microsoft.com/en-us/library/jj612800.aspx
Tested B Correct!
I had this question in my exam but none of these answers!!
Marwan, i think you had in the answers, the powershell way that Bobsmith say just above.
I think Microsoft change sometimes between this two way to do with this question.
For the next time (I don’t know if you had your certification), remember both solutions 😉
Question changed. which one will be the answer?
1. Run the Set-IscsiVirtualDisk cmdlet and specify the -DevicePath parameter.
2. Run the iscsicpl command and specify the virtualdisklun parameter.
3. Modify the properties of the itgt ISCSI target.
4. Run the Set-VirtualDisk cmdlet and specify the -Uniqueld parameter.
I believe in your scenario 3 is correct. Note that in the original question the GUI option is to change the vhd properties. Here, option 3, its the GUI option to change the “itgt ISCSI target”. If you open File and Storage, you can go to the properties of the iSCSI target and change the LUN #.
The question had changed for me as well. I believe based on the article below the answer should be 1 or A from what Mike listed.
https://technet.microsoft.com/en-us/library/jj612817.aspx
You actually change LUN settings on a virtual disk, not on a target. So answer is B (if GUI is not optional, then powershell Add-IscsiVirtualDiskTargetMapping would be the correct answer)
The only command I could find that allows LUN # assignment is:
Add-IscsiVirtualDiskTargetMapping
This example associates the VHD with the path E:\Temp\vhd1.vhdx to the target named TargetOne, and sets the LUN to 0. It is important that the LUN number for a given target is unique.
Add-IscsiVirtualDiskTargetMapping -TargetName “TargetOne” -DevicePath “E:\Temp\vhd1.vhdx” -Lun 0
http://www.lazywinadmin.com/2013/07/create-iscsi-target-using-powershell-on.html
So, I believe the Answer is A. As listed in the original question. As Set-ISCSIVirtualDisk & Set-VirtualDisk offer no such options.
And you will note in the question that the VHD was “removed” from LON-DC1 so “Adding” it via the “ADD-iSCSIVirtualDiskTargetMapping” command above with a new LUN number makes sense. Especially vs. a SET-
I am not an iSCSI person but I was a SAN guy for 7 years and you always had to remove the LUN (unmask) from the host (Target in this case) and set the LUN number when re-masking it to the target to change the LUN #. You could not change the LUN numbering ‘after’ it was assigned. So the key to this question is that it was removed from the host and you have to put it back with a new LUN #.
B
it is B. Modify the properties of the VHD. Right click go to properties and there is a LUN box
Agreed
Answer is A.
https://technet.microsoft.com/en-us/library/gg232626(v=ws.10).aspx
The option to change the LUN of a virtual disk is only available when you view the virtual disk Properties from the Devices node in the Microsoft iSCSI Software Target console.
I’m looking at this now and you can only view the lun id in isci initiator there is no option to change anything regardless of what the link says
However quite clearly you CAN change the lun id from the vdisk properties in Server Manager.
That is from 2010 and is talking about the downloadable ISCSI software target software, not the ISCSi target service which is integrated into 2012 server.
Di is correct , answer is B , tested in my VM
The option to “change” the LUN of a virtual disk is only available when you view the virtual disk Properties from the Devices node in the Microsoft iSCSI Software Target console. However we are not “changing” a LUN value, we are “assigning” a LUN value.
Pls stop posting misinformation
that is referring to the downloadable ISCSI software target software, not the ISCSi target service which is integrated into 2012 server
Guys, read the question!
First there is virtualiSCSI1 (which has LUN 0), if you add virtualiSCSI2 it will have LUN 1. take away virtualiSCSI1
try to update to 0 using the properties and windows will tell you that there already a LUN0.
you need to use powershell!
B
All these people saying that B is correct because they tested it in their lab is complete bullshit. If you actually set up a lab and test this, you will see that after you remove iscsi1, if you go to the properties of iscsi2 and try to change the LUN ID from 1 to 0, it won’t let you, prompts with an error saying that LUN 0 already exists.
Not sure what’s the proper way to change it, but it’s definitely not B. I guess Add-IscsiVirtualDiskTargetMapping -TargetName would do the trick but it’s not listed here.
No, it is B.
In the Server Manager gui I removed VirtualiSCSI1, ticking the check box “Delete the iSCSI virtual disk file from the disk”, although I doubt if this matters.
After VirtualiSCSI1 was gone I went to the properties of VirtualiSCSI2 and tried to change the LUN ID to 0. At first I got an error “The LUN 0 conflicts with another virtual disk …”
But I clicked the refresh icon, waited, then I was able to go to the properties of VirtualiSCSI2 and change the LUN ID to 0.
No, it is B.
In the Server Manager gui I removed VirtualiSCSI1, ticking the check box “Delete the iSCSI virtual disk file from the disk”, although I doubt if this matters.
After VirtualiSCSI1 was gone I went to the properties of VirtualiSCSI2 and tried to change the LUN ID to 0. At first I got an error “The LUN 0 conflicts with another virtual disk …”
But I clicked the refresh icon, waited, then I was able to go to the properties of VirtualiSCSI2 and change the LUN ID to 0.
No, it is B.
In the Server Manager gui I removed VirtualiSCSI1, ticking the check box “Delete the iSCSI virtual disk file from the disk”, although I doubt if this matters.
After VirtualiSCSI1 was gone I went to the properties of VirtualiSCSI2 and tried to change the LUN ID to 0. At first I got an error “The LUN 0 conflicts with another virtual disk …”
But I clicked the refresh icon, waited, then I was able to go to the properties of VirtualiSCSI2 and change the LUN ID to 0.
Er sorry for spamming! Clicked refresh, didn’t see my update so tried again
The Add-IscsiVirtualDiskTargetMapping cmdlet assigns a virtual disk to an iSCSI target. Once a virtual disk has been assigned to a target, and after the iSCSi initiator connects to that target, the iSCSI initiator can access the virtual disk. All of the virtual disks assigned to the same iSCSI target will be accessible by the connected iSCSI initiator.
anser :c