Date: Thu, 30 Jun 2011 06:49:25 -0400 (EDT) From: Daniel Feenberg <feenberg@nber.org> To: perryh@pluto.rain.com Cc: freebsd-net@freebsd.org, korvus@comcast.net, freebsd-questions@freebsd.org Subject: Re: Question about NIC link state initialization Message-ID: <alpine.LFD.2.00.1106300644320.21262@nber9.nber.org> In-Reply-To: <4e0c0548.eW27hshSLoLhhTu1%perryh@pluto.rain.com> References: <4E0B540B.3090400@comcast.net> <4e0c0548.eW27hshSLoLhhTu1%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 29 Jun 2011, perryh@pluto.rain.com wrote: > Steve Polyack <korvus@comcast.net> wrote: > >> ... An occaisional fat-finger in /etc/fstab may cause one to >> end up in single-user mode ... some of these systems have a LOM >> (lights-out management) controller which shares the system's >> on-board NICs ... when the system drops out of init(8) and into >> single-user mode, the links on the interfaces never come up, >> and therefore the LOM becomes inaccessible. >> >> ... all one has to do is run ifconfig to cause the NIC's links to >> come up ... why do we have to run ifconfig(8) to bring the links >> up on the attached interfaces? > > When trying to troubleshoot a problem that was known or suspected to > involve the network or its hardware, one might not _want_ the NICs Well, maybe, but if the system needs to boot into multi-user mode for the LOM to be available, what is the need for the LOM? At that point you can do everything you might need through the OS interface. Can I ask what is the brand of this so-called LOM? Is there any documentation implying something more useful? Do they describe doing a bare metal install of an OS? Daniel Feenberg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LFD.2.00.1106300644320.21262>