On Wed, 17 Oct 2007, Garrett D'Amore wrote:
> Paul Jakma wrote:
> > On Wed, 17 Oct 2007, Bill Sommerfeld wrote:
> >
> > > one implication of this is that, when this is in use, the NIC cannot be
> > > part of a L2 aggregation (because the upstream switch will load-spread
> > > some of the management traffic flows to other ports in the aggregation).
> > >
> > > And using it with other L2/L3 redundancy technologies (such as IPMP and
> > > OSPF-MP) is going to be tricky (the shared management IP address must
> > > not be seen as reachable via other NICs).
> >
> > IMLU: These don't preclude use of AMT in normal operation - the OS can
> > always redirect packets to AMT that didn't get hijacked.
> >
> > Does obviously preclude reliable Out-of-Band use of AMT. Indeed, I really
> > wonder how the LOM firmware can know whether or not it needs to do ARP for a
> > shared IP.
>
> There is a private method by which the firmware decides whether the host OS is
> alive and healthy. If so, then the host does this work. If not, then the
> firmware takes over.
>
I have been looking for a place to ask this quesiton, and this might
be it: What occurs if the machine is suspended and the NIC is still
hot (maybe WOL enabled). Will the ME also be running? If so, the OS
is not, will it still know that OS is alive and healthy, or decide it
is bad and try and reboot? Will it be able to generate a PME and
resume? (and maybe a host of other questions surrounding suspended
machines).
---- Randy
> -- Garrett
> >
> > regards,
>
