Do you see other hosts on the clariion using the same SP ports? If so, it's a Zoning issue - did you save and apply? Do you have sufficient licenses on the switch.
See, I felt the same way. That it had to be zoning. But again, I know that the WWN's are correct. Especially after changing out the HBA to the Emulex because like I said it stands out from the other QLogics. This blade Alias is zoned with the exact same aliases for SPA and SPB that the 4 other blades in this same chasis are pointing too in other zones. I have saved the changes and also the zone config several times wondering if it just didn't take. I even rebooting the fabric switches. The particular chasis that these blades are in are all going through the same two SSM modules which I have setup for "Access Gateway" mode which puts it just a passthrough switch. I do see all other HBA's for all other blades in both the switch and in Navisphere. It's just this one that I can see in switch but nothing in Navisphere. I will double check the version of these switches as well as the licensing. Should be ok but at this point it's worth a quick look.
When checking the zoning I recommend using the command nszonemember <wwn>. This directly queries the fabric nameserver and shows all active connected ports.
What firmware are you using on the Switch? There is a bug with state change notification which could cause this behaviour. It was fixed recently in 6.3.1a.
When scanning for luns on the VMware host please follow the steps mentioned in http://communities.vmware.com/thread/8843
hope that helps
Message was edited by: bernd (typos)
Also, I read the article in regards to the rescanning of HBA's in VCenter. But I beleive that's addressing VCenter seeing allocated LUNS in which I haven't gotten this far yet. At this point it seems that the issue can't be at the VMWare side because I haven't been able to present any LUNs to the ESXi host yet. VCenter just sees what I present to it really.
Yep, more than once. I save the Active Config and also selected Enable just in case. It is the only Zone config that I have.
i have experienced the issue where zoning is correct but the host is just not logging into the storage frame. it seems that the naem server is not being updated and a way to "force" and update is to block/unblock an ISL. I beleive that at the highest firmware levels this issue is "fixed" well mostly anyway. I think someone posted something to this effect.