[Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Leif Nixon nixon at nsc.liu.seTue Oct 27 06:13:02 PDT 2009
- Previous message: [Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
- Next message: [Beowulf] Tilera targets Intel, AMD with 100-core processor
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rahul Nabar <rpnabar at gmail.com> writes: > (I know Joe Landman and others had warned me against this but I tried > to start with configuring a single shared NIC and then go for two > NICs. Just keeping things simple to start with.) Using shared NICs is the *complicated* alternative. You are exposing yourself to a lot of potential weird effects. I prefer having the IPMI stuff on a separate NIC that is not only dedicated, but also totally unreachable from the host OS. If somebody roots a node, they shouldn't get access to the IPMI network. -- / Swedish National Infrastructure for Computing Leif Nixon - Security officer < National Supercomputer Centre \ Nordic Data Grid Facility
- Previous message: [Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
- Next message: [Beowulf] Tilera targets Intel, AMD with 100-core processor
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
