"Stephane, need to confirm but it could be an open issue where target information is not fully visible, in VI client interface, for some paths. This should however not impact paths available or connectivity to the array. You can also see the iSCSI session information from the MD3000i Storage Manager (MDSM) application and hence relate the connections from host interfaces to MD3000i ports."
"Stephane, In an ideal condition, there will be one active path and three standby paths. There is no known issue on this so far. are you seeing the similar behavior in other stup as well. Let me know."
"We use a "Fixed" policy in VMware to access the LUN."
"Thanks for your reply.We use a "Fixed" policy in VMware to access the LUN.On the first server being installed, the display is now correct, I can see all the targets : we have one "Active I/O" path, one "Active", and two "Stand by". It seems correct to me. 12 paths for 3 LUNs with four controllers, normal.On the second server installed last week (same configuration), the display is incorrect.There is the same display failure, only one path with target full information, the others are blank. And we see 16 paths, because the host sees the 31 LUN. Strange.I have to set up the third and last server this week, I will let you know if there is the same behavior."
"Are there any Dell recommendations as whether to use fixed, MRU or Round Robin against an MD3000i? Does one also need to correlate the MSDM "preferred owner" policy with the preferred path in ESX?"