topic Re: ILO/itool problem on new blade in BladeSystem - General

ILO/itool problem on new blade

Eric Junkermann — Wed, 21 Jan 2009 15:48:11 GMT

We have a new blade to set up (first time we've done this), we have got as far as the itool TUI screens in the ILO serial console, and we could probably figure it out if we didn't have to keep clicking the mouse before every keystroke - if we don't do that keystrokes are ignored.

Did we do something wrong, or is there a better way to do it?

Thanx,

Eric

Re: ILO/itool problem on new blade

Steven E. Protter — Wed, 21 Jan 2009 15:52:12 GMT

Shalom,

First time ilo setup is best done directly connected to the system. At the console. Most ilo cards have an interface that negates the requirement for mouse use. That lets you set up the IP address. After this is done, the rest of the process can be done via ilo web interface.

SEP

Re: ILO/itool problem on new blade

Torsten. — Wed, 21 Jan 2009 18:21:52 GMT

What model is it?

BL860c or BL870c?

Try the internal serial connection or maybe better a console emulation directly to the front serial port (dongle) first.

For any other model please ask in Server->blade forum.

Re: ILO/itool problem on new blade

Eric Junkermann — Mon, 26 Jan 2009 14:35:28 GMT

Thanx for the answers, though they didn't actually solve anything - we were trying to use the serial console (no mouse required), but the window in ILO was behaving as if it always lost focus, needing a mouse click to restore focus before each keystroke. Strange, but it turned out to be something about the PC we were using - works OK on another PC - still don't know why.

SEP - what ILO web inerface were you referring to?

Eric

Re: ILO/itool problem on new blade

Gatis Visnevskis Gasha — Tue, 27 Jan 2009 14:20:33 GMT

I solved similar issues with downgrading JAVA JRE from 1.6.0 to 1.4.2

Console was loosing characters and some other behavior...

Re: ILO/itool problem on new blade

Eric Junkermann — Wed, 31 Mar 2010 14:57:28 GMT

turned out to be something about the PC we were using - works OK on another PC - still don't know why