I'll comment on what I've seen on our VNXs (iSCSI):

- Stale DGC LUNZ devices in Device Manager (View > Show Hidden Devices) > Disk Drives.  I've removed them, rebooted and then the host is registered.  I've seen the same where initiators are logged in but not registered.

- Unisphere Bug: I have a case open with EE where new hosts will absolutely not show up as REGISTERED until I log off and log back on to Unisphere.  Extremely frustrating.

Ben

Thanks for the info!  I've tried rebooting the server in question and simply cannot get it to register.  Can you confirm at what point you install the Agent?  Is it after you input all the info into Windows iSCSI initiator?  (discovery portal, connect to the targets, etc).  Does this matter?  Also if it helps, we are not using Power Path.

It doesn't matter when you install the agent. Since you already discovered the targets restart the Unisphere Agent service and see if that works. My guess is it won't since you tried a host reboot but not sure if you rebooted the host after you discovered the target array.

I've seen this before and somehow after a few hours the host showed as registered in Unisphere.

If the above still doesn't work reboot the management service on each SP. You can do this any time and it doesn't impact anything. Just go to https://spA-IP/setup. Do the same on SP-B. Wait a few minutes, log back in to Unisphere and see if that worked.

The Agent is optional.  I'm not using power path either.  Did you remove the DGC LUNZ devices from device manager and reboot?

I did take a look at the server utility.  I asked someone at EMC about using the agent vs. the server utility and was told the agent was preferred but didn't give any particular reason.  Do you use the Server Utility or the Agent?  Or neither?

did you try Unisphere server utility ?  It has a pretty good wizard that should walk you through the steps

https://support.emc.com/search/?text=unisphere%20server%20utility&resource=DOWN

I did remove the disks and reboot; no luck.  I am going to rebuild the VM from scratch and go through the whole process again.

I am very, very interested in your comment about the agent being optional.  What do you lose, if anything, by manually registering your initiators and not even using the Agent?  If it is the case that the Agent isn't doing anything for me I might just update our documentation to not even install it.

run the utility, it should help you discover the target (Select "Configure iSCSI option)

i use the utility for "one time" registration, i don't care about getting host device information (IE: LUN 7 is drive letter F:\ on a windows box) as that requires the agent.

Thank you very much!  I will check out the server utility again and try to use it to register.  It sounds like we really won't be missing anything by not using the Agent.

Question:  when setting up a new Windows server, at what point do you install and run the server utility?  Do you do it after you set up the Microsoft iSCSI initiator? (discovery portal, etc).

+1 for restarting starting the management service. That has fixed things for me a few times too.

Ben

Sent from my mobile device

Restarting the management on the SPs did the trick; thanks for the assistance; greatly appreciated