Wrong answer. Care to try again?
EMC does not license MPIO, they have their own proprietary multipathing software - powerpath (well there is powerpath for iSCSI, which does use Microsoft MPIO, but that's another story and the term HBA was used here so I don't think so).
Let's step back a minute and parse this out:
DUAL HBA's connected to a Clariion CX600
- Multipath
After doing a Flare OS upgrade to the Clariion Array
- Change to the environment
we are seeing the disks belonging to the other node in the cluster as "Not Initilaized, Unallocated".
- yup, 820127 describes an issue where vds.exe incorrectly
translates the disk status of "ERROR_BUSY". Hmmm, but is this your issue?
why don't I see this with the cluster nodes that only have a single HBA in them?
- The difference between the single HBA and dual HBAs is the path management software.
Do we see that not initialized, unallocated wording in any other situations?
- yup, when there's a pathing/zoning/mapping issue
I suspect it's a bit more than the vds issue.
I have been told this is a Microsoft issue...
- Let me guess, by EMC tech support. Now, if you ask MS, I bet they'll say it's an EMC issue. About as productive as setting two phones to call forward to each other and dialing one of them, isn't it?
You could probably save yourself a lot of frustration by cranking up the logging on the HBAs and viewing the status code that gets returned in both the single path and dual path situations. If the single path configuration returns the same status as the dual path configuration, and it's ERROR_BUSY (the HBA vendor should have documentation on how to break out the scsistat, srbstat, and sense code data. If it gets logged is scsiportlogerror format, log at offset 0x38 for 0x08). If say, both configurations don't send the same error code and the dual configuration is sending busy, then it would be vds.exe. If not, you have issues in the path.
