Ok, I know you guys are out there doing UCS and regular storage labs because all the time slots are always booked up, so I'm hoping a couple of you might be able to help me figure out if it's me or my lab set up that's not working.
A few times, I've been able to score a last minute UCS or N2k/SAN lab and in every single one of these, I've never been able to successfully connect to the storage. In one case, the FC interfaces were stuck in an init state and one of the responses I got from my trouble ticket was to check out the forums (well, here I am). Incidentally, I discovered the issue doing the very first UCS Storage lab which is a simple configure interfaces as F ports and make sure the FC RAID FLOGIs, which of course, it didn't. But hey, if anyone in the community knows a neat trick to force these F mode, hard set speed 2000 ports to just come up (like they normally just do when the storage is working properly), I'm all ears.
Rant aside, all the other times I've attempted a connection, I can see the FC RAID does successfully FLOGI, but when I do a "sh fcns database", they are never shown as targets. I can proceed to set up the zoneset/zones or even in the iSCSI lab, configure everything exactly like the solutions say to do it, but I've never been able to connect to the storage. As I stated, the FCNS database doesn't show that the storage devices are targets, which is what I thought I would see, but I do see my initiators listed as "init" devices.
Anyone else seen this behavior in the lab, and were you ever able to connect to the storage? These labs (5 in total) have all been done in the last 2 weeks.