A quick search on the Emulex web site gives a short "how-to" for the emlxdrv utility.
http://searchwww.emulex.com/search?q=cache:GwPPMG7FOpYJ:www.emulex.com/support/solaris/lpfc_100_rbyd.pdf+emlxdrv&access=p&output=xml_no_dtd&site=default_collection&ie=UTF-8&client=default_frontend&proxystylesheet=default_frontend&oe=UTF-8 It looks like an interaction by the user is required. When the SUNWemlxs package is installed, it steps through a list of supported HBAs. If those HBAs have entries in the /etc/driver_aliases binding them to the lpfc driver they will be ignored, else an entry will be added binding it to the Sun FC drivers. If you want to use only the Emulex lpfc, you will probably want to remove the SUNWemlxs package. I have not played with the emlxdrv utility, so I don't know if it removes entries from the "private" /etc/ driver files. Maybe Emulex can give you some information there. Vic Engle wrote: > The emlxdrv utility may be used to configure a host to use either emlxs or > lpfc for Emulex HBAs. The emlxs driver is used by default. What does emlxdrv > do to configure one driver or the other? Is it possible to script this change > so that a jumpstart finish script could configure a host being installed to > use the lpfc driver rather than emlxs? > > Granted, using the leadville driver would be preferred most of the time but > for the exceptions it would be nice to be able to automate the driver > selection. > > > This message posted from opensolaris.org > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
