Well if you say FC, you are talking enterprise, thus resiliency thus multipath... As many agree on this list. To accommodate "people from around the world" we should only test it at the conceptual level.
* Purpose of MP. * Name of OSS implementation. No configuration. * Understand that vendors may use other tools That's it. P.S. Me too, I have no way to test FC set-up given our testlab. On 9-6-2013 15:50, G. Matthew Rice wrote:
On Sun, Jun 9, 2013 at 5:48 AM, Reinier Kleipool <rein...@opensourceacademy.eu <mailto:rein...@opensourceacademy.eu>> wrote:Yes the Key Knowledge Areas looks better. I agree that iscsd and iscsid.conf should be included. Further I would (And many others on this list...) like to see "Awareness of the purpose of multipathing in FC" added as well. Maybe add to term and utilities "device-mapper-multipath, mpathconf, /etc/multipath.conf, awareness of vendor implementations"Are we not running the risk of making LPIC-2 too enterprise-y? Remember, we have people from around the world taking these exams. And many of them are playing catchup with the technology.Thoughts everyone? --matt
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
