You command is not being ignored. There is nothing visible to the HBA for it to configure.
So the devices under an HBA show up once they are visible to the HBA. I never look at the HBA occupant column for the HBA CX line. I normally look for the Type column: c1 fc-private c1::21000020379cb9bb disk connected configured unknown c4 fc-fabric connected unconfigured unknown c5 fc connected unconfigured unknown C1 is a 280r internal controller C4 is a HBA attached to a switch with no targets C5 is a HBA that has nothing connected Now in the case of C4, when I have it in a zone by itself, I get only this line: c4 fc-fabric connected unconfigured unknown But when I add some devices into the zone (I'm not touching or configuring anything on the host, only changing the zone on the switch), I get this: c4 fc-fabric connected unconfigured unknown c4::100000e0024302c0 tape connected unconfigured unknown c4::210000008708d98d disk connected unconfigured unknown Then if I perform a "cfgadm -c configure c4" I get this: c4 fc-fabric connected configured unknown c4::100000e0024302c0 tape connected configured unknown c4::210000008708d98d disk connected configured unknown So you see how the WWNs of the targets show up before the HBA is "configured". The act of "configure" against the HBA port is essentially telling the leadville driver stack to present the targets off of the HBA up to the OS. In your case where the initial cfgadm -al is not showing any additional devices, it tells me the zoning on your switch is preventing the HBA from communicating with the storage. Another way of testing this is to use the OBP "probe-scsi-all" command and see if the storage appears from there. This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
