Bomb_29390e

updated

17 years ago

B

Bomb_29390e

2 Intern

193 Posts

0

374

June 30th, 2009 16:00

Bound Volume/Devices

i set my iscsi initiator succsfully with all settings on the initators and the targets )SAN). in some reason in additon to to my Volume D:\ - which is the thin lun i created, i also have another mount point look like this:
\\?mpio#disk&ven_dgc&prod_lunz&rev_0428#1&7f6ac24&o&305f325...
i read a bit and found that this reffer to a LUNZ kind of a fake logical unit zero
presented to the host to provide a path for host software to send
configuration commands to the array when no physical logical unit
zero is available to the host. - how do i get rid of this?
i verified this by going to the disk mgmt and can see that there is : disk 1 - unknown, tried to rescan disks, reboot the machine, rediscover and configure target in the iscsi initator software and still when using the bind all button it still shows under devices - any idea why? - please help
  • kelleg

    6 Operator

    4537 Posts

    198

    0

    Posted July 1st, 2009 08:00

    When you first connect a new host to any array, once the new host is logged in and registered, the array will present a LUNZ to the host, so that it has a path to follow. Once you create a storage group, add the host to the storage group and then add one real LUN to the storage group, the first LUN you add gets assigned Host Lun (HLU) zero. YOu can see this in the Storage Group properties for the Storage Group in the right-hand window - all the way on the right - see the HLU column. Once you have a real LUN in the storage group and that LUN is assigned to HLU zero, the LUNZ will disappear.

    You need to be aware that if you ever remove the HLU zero LUN from the storage group, that you will then see the LUNZ again.

    glen