Hello Shabery, Here are the answers to your questions: The qla2300 driver does not work with the traffic manager.
There is Qlogic supplied FCODE for when using the qlc driver. It will give the OBP hardware path of QLGC,qlc. The Qlogic "channel" fcode gives the OBP name of QLGC,qla. But changing around the FCODE is not necessary to use the qlc driver. The FCODE only provides the appropriate hooks for performing a boot from SAN setup and the OBP name. From the QLogic download page select the HBA model. At the bottom of that first page are the download links for the different boot code you can load onto the HBA. Pull down the FCODE you want and then follow the link above that for the OS rev you have. From there you will find the sansurfer CLI (scli) utility which will allow you to flash the FCODE onto the HBA. With the qla2300 driver you can use the SANSurfer GUI, or SANSurfer CLI it view the available devices, or you can use the driver's utilities from under /opt/QLogic_Corporation/drvutil/qla2300. There is documentation for those utilities in the same directory. The output from the driver is placed in the messages file. If you want to use the qlc driver with the QLogic HBAs, follow the same software install/update procedure as you would for a Sun HBA and then pkgrm the QLA2300 driver package and reconfigure reboot. Now luxadm will not work for updating the FCODE on the QLogic adapers but there are qlc driver ioctls to allow the SanSurfer CLI and GUI to update the FCODE. Lyle This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
