The centralized management console announced that it was executing my tasks, the access lights started flashing on the drives, and then the console (and Java) crashed. After I rebooted the server, I was pleasantly surprised that there was no lasting damage from the crash. I launched the centralized management console and created a new iSCSI server. I was immediately able to access it from the Microsoft iSCSI Initiator on my Windows server.
(I can't believe he was happy with this!!!! )
This post had a similar expereince
The only problem I ran into was that occasionally the console wouldn't start and I needed to terminate the javaw.exe process in Task Manager before restarting the console.
Anyways, in the Eweek article he liked the Idea of the architecture of the LeftHand SAN. He also received a dud of a unit, this is what he wrote.
The second server started, but failed to recognize the array controller and therefore didn’t boot completely.
Of course, the first thing I did then was take the server apart, at which point I noticed that the board containing the SAN/iQ software had fallen off of the P400 RAID controller—obviously a casualty of rough handling during shipping. Popping it back on did not solve the problem, but after an e-mail and a quick call, a new controller and a third server were on their way. After I installed the new controller, the server booted up smoothly.
Later on he ended up having a little bit of a support problem, he wrote
The only unpleasantness that I have to report is that it took tech support more than 48 hours to respond to an e-mail requesting access to the support Website. I think it is fair to say that any company that shells out $30K for storage will want access to the documentation within 48 minutes rather than 48 hours.
He was also unable to set up the SMTP for sending alerts to his email address.
He was impressed by the performance and by the management of the device.