From owner-freebsd-proliant@FreeBSD.ORG Fri Jan 20 15:07:41 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E0BF16A41F for ; Fri, 20 Jan 2006 15:07:41 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CC6B43D4C for ; Fri, 20 Jan 2006 15:07:40 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so324196wxc for ; Fri, 20 Jan 2006 07:07:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=R0WhS+JwAQL08IWRWGSkfh8C/FrNIpBoEX4eQ+qTwDeuMSeGzcymkF/qykTGLB/0uVmIh0HPfOUhxYQblcK+DqihsYBpUkrn3S5PHvAmXyPpmkmD4c3wxeCJpiE4ct8kllS7GkIRSBhu6N1FoYqJFVzb2ckQncRUltoy+aM6t8k= Received: by 10.70.131.17 with SMTP id e17mr2267435wxd; Fri, 20 Jan 2006 07:07:40 -0800 (PST) Received: by 10.70.15.14 with HTTP; Fri, 20 Jan 2006 07:07:39 -0800 (PST) Message-ID: <6863f0c90601200707q247cf9fbj368af76d196a0783@mail.gmail.com> Date: Fri, 20 Jan 2006 09:07:39 -0600 From: jmc To: "Marc G. Fournier" In-Reply-To: <20060119214816.X28752@ganymede.hub.org> MIME-Version: 1.0 References: <20060119214816.X28752@ganymede.hub.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-proliant@freebsd.org Subject: Re: TIP: iLO remcons doesn't connect consistently X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 15:07:41 -0000 One thing to realize is that iLO is ON even if the server is powered off. However, when you pull the power plug on the server, it will remove power t= o iLO (obviously) and hence plugging it back in will, in effect, "reboot" the iLO. Also, iLO only allows a single REMCONS session at a time. If you have one session running, you won't be able to start another one until the first one is closed. On 1/19/06, Marc G. Fournier wrote: > > > Just to document this, in case others hit the situation ... > > The one 'issue' that I've had so far with the new DL360 G4p was that when > I tried to enabled 'remcons' from an ssh connection into iLO, it wouldn't > always give me a console ... if I unplugged the server from the wall, and > re-plugged it in and tried then, it worked fine .. if I unplugged it yet > again and plugged it back in again, it *might* work, it might now ... > > After some searching, I found something that *sounded* similar on HPs > forums, where the suggested fix was to go through the web interface, unde= r > Network Settings, and make sure you disable the WINS stuff ... > > *So* far, each time I've unplugged/plugged it back in again, I've been > able to successfully get a remcons through iLO ... going to try it a few > more times before I ship it out, but *so far* things seem to be good ... > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.or= g > ) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: > 7615664 > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.or= g > " >