There should NEVER be a reason to modify the /etc/driver_aliases for a production configuration. If there is trouble with QLogic cards and the qlc driver not attaching then open a service request on the QLogic website.
With that said. There were some early versions of the FCODE included on the QLA/E246X (i.e. 4 gig) qlogic cards that had a bug. You would have to load the QLogic driver, flash the QLogic card with latest multi-boot image and then pkgrm the QLogic driver. Then after another boot the card will have the correct OBP compatible properties for qlc to properly bind. I've got a QLogic knowledge base article getting reviewed at this time and it covers this situation. If you have the QLA2300 driver installed on a host and you have QLogic branded HBAs in there, the qla2300 driver will bind. If you remove the qla2300 driver and you are on solaris 8 or 9 with the SFS software installed or just patch up a Solaris 10 install, then the qlc driver will bind to the QLogic branded cards. It's pretty simple and if the driver binding does not work then just open a support case with QLogic. This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
