What’s then not clear is how the ongoing status of the device can be managed.
Reduced Management – if the DroboPro is to be connected to an ESX server, then the documentation indicates the USB cable should be removed.Be aware – unplugging the USB cable seems to cause the Drobo to immediately reboot. USB and iSCSI Configuration – it isn’t clear whether the Drobo Dashboard can configure the DroboPro over either the USB connection or the iSCSI connection or whether USB connectivity needs to be retained for future configuration tasks.In any case, I now have visibility of my DroboPro within ESXi. Presumably with the Drobo Elite the multi-user functionality is achieved by enabling multiple targets per Drobo, each mapped to a separate user. This method of presentation doesn’t necessarily cause a problem, but is just a different way of presenting the LUNs. The DroboPro presents all its iSCSI LUNs on the same target (in this instance number 3) and so the LUNs are numbered from 0. The Target setting is analagous to a storage port, typically a physical port on large fibre channel arrays. In standard Controller/Target/LUN or CxTyLz/CxTyDz methodology, the ix4 disks are using separate targets to map out each iSCSI LUN, with the LUN number always ‘0’. The difference is in the way the DroboPro is choosing to present iSCSI devices and the Runtime Name column gives a clue. Compare this to the LUNs presented from my ix4-200d, which has three LUNs all numbered ‘0’. So far, I’ve configured eight 2TB LUNs (although the DroboPro itself only has a capacity of 5TB, 2x 2TB and a single 1TB drive) which are numbered 0-7 the LUN column on the screenshot. See the attached screenshot image taken from my production ESXi server. I’ve now managed to get the ‘Pro connected and visible within ESXi. Previously I discussed a few frustrations with connecting my new DroboPro to ESXi, the target environment for my new device.
DROBO DASHBOARD CANNOT CONNECT TO IP ADDRESS SERIES
This is the second in a series of posts looking at the DroboPro from Data Robotics Inc.
0 kommentar(er)
