OK... So the Apple Care support call was not that productive. They were very nice, however, they basically had no idea what I was talking about. I was generally asking about the difference in LUN handling from 10.6 to 10.7 and they gave me the canned response of "you are not using Apple Hardware so we can't really help you, we are really sorry...." This was after being transferred to the "Enterprise Storage Group" or something like that.
So in my travels I found a tech note from another apple list which basically explains what happened between 10.6 and 10.7.
I'm not "that hardcore" but some of you guys will really get what is going on here. I'm a bit of an IT neanderthal but what has changed as some here have pointed to is that in 10.7 the OS does its own FC multipathing.
Here is what Manjo Radhakrishnan from Apple said...
"10.7 does its own FC multipathing. This has changed from 10.6 which did target based multipathing ( based on WWNN ). On 10.7 this has changed to lun based multipathing ( based on the unique lun identifier in the device identification VPD page ).
If the target supports ALUA ( Asymmetric logical unit access ), the host will do IOs only to the target ports configured as "Active-Optimized" for a particular lun. If there is no ALUA support, all paths to a particular lun will be considered active-optimized and IOs will be done across all the paths.
Ideally if the target does not support ALUA, you should configure the luns such that a lun is visible only across the ports of one of the target controllers ( lun affinity ) to prevent lun thrashing."
So here is the link to the thread...
http://lists.apple.com/archives/ata-scsi-dev/2011/Jul/msg00001.html
If someone can translate this from smart-guy into dummy-end-user and tell me how to fix my infortrend boxes under 10.7 I'll buy you a bottle of really nice tequila (or several cases of yoohoo).
thanks!
Jonathon