Date: Tue, 12 Sep 2006 18:38:01 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: jmc <jcagle@gmail.com> Cc: freebsd-proliant@freebsd.org Subject: Re: ssh ilo question Message-ID: <20060912183211.K36880@ganymede.hub.org> In-Reply-To: <6863f0c90609121425n330c863cj71e41edc36ec552@mail.gmail.com> References: <20060912092617.F2717@shanty.ipnstock.com> <6863f0c90609120640w15be76a2sf79b70936e6897a5@mail.gmail.com> <20060912122313.T36880@ganymede.hub.org> <6863f0c90609121425n330c863cj71e41edc36ec552@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Sep 2006, jmc wrote:
> One really cool feature is "Shared network port". This means that the
> iLO Ethernet traffic can run across the NIC1 link, so that it doesn't
> require an additional Ethernet port for each server. You can configure
> an iLO VLAN tag so that the iLO management traffic is kept separate by
> the ethernet switch.
* Embedded system health provides access to basic hardware status
independent of the operating system
this one is very nice to see ...
* Shared Network Port now supports full access to iLO 2 via the
browser and scripting interfaces
I thought that iLO-1 supported this already, but someone recently reported
that as soon as the operating starts up, it was locking him out of the
SNP? Do you know if iLO-2 fixes that? Or are we talking about two
different things here?
* The iLO 2 browser user interface is updated to provide easier to use
web pages and consistency with other ProLiant Essentials products
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060912183211.K36880>