We have two HP EVA 6000 here, plus two MPX 100 iSCSI Connectivity boxes.
I my first experiments with iSCSI I failed to present a LUN to a host using
CommandView 8.0, but I was able to do so when using the CLI (Command Line
Interface) on the MPX 100 box.
Having opened a call at HP showed up no more than the statement "It must
work!". However a on-site technican confirmed that it did not. As there were
no reasonable-sounding suggestions, I agreed with the technican that there is
nothing promising to do at the moment (this was a productive environment,
where the suggested re-cabling of FC and adding new switches was not a welcome
Today (after some pause) I made a network trace between the CommandView 8.0.2
machine and the MPX100' management port. I always wondered that there was no
authentication information in CommandView to configure for admin access to the
MPX 100. The network trace suggested that HP uses some proprietary binary
protocol to communicate with the MPX 100.
I had been hoping that I could read the problem from the communication between
the MPX 100 and CommandView, but the results left an uneasy feeling that
anyone who knows about the proprietary protocol can reconfigure the MPX 100
boxes via network.
Having expeienced the "HP Secure Web Console" I wonder why HP still does such
And before you ask: The error message in ComandView reads: "The virtual disk
could not be presented to a host"
Note the highly specific wording regarding the LUN, the host and the reason
and detail for the failure!
(CommandView 8.0.2 still uses invalid CSS stylesheets; If you are using
Firefox 3, open the "Tools->Error Console" to see)
||1/16/2009 12:04:05 PM