Penguin
Annotated edit history of iLO version 4, including all changes. View license author blame.
Rev Author # Line
1 JohnMcPherson 1 !!! iLO - Integrated Lights Out
2
3 iLO is the management interface used on many HewlettPackard servers. These often allow you to remotely power a machine up or down, and connect to the machine's local console.
4
5 !! Random Notes
6
2 AristotlePagaltzis 7 "<tt>ssh $ilo</tt>" returns "<tt>Received disconnect from ip.ad.dr.ess: 11: Authentication failed</tt>":
1 JohnMcPherson 8
2 AristotlePagaltzis 9 Check if you have several [SSHKeys] in your [SSH] agent (eg. with "<tt>ssh-add -L</tt>"). Each time your agent tries a key that is not in the iLO's list of authorised keys counts as a failure, and after 3 failures it will close the connection. Either install your keys in the iLO's key management system, or run [SSH] without your agent:
10
11 <pre>
12 SSH_AUTH_SOCK= ssh $ilo
13 </pre>
14
15 "<tt>ssh $ilo</tt>" returns "<tt>shell request failed on channel 0</tt>":
16
17 If you run "<tt>ssh -v $ilo</tt>", you'll see that the last debug message before failing is something like
18
19 <pre>
20 debug1: Sending env LANG = en_NZ.UTF-8
21 </pre>
22
4 AristotlePagaltzis 23 This confuses old versions of the iLO. If you don't want to install a newer iLO firmware (you can get it from the [HP] website), you can work around this by completely unsetting the <tt>LANG</tt> EnvironmentVariable:
2 AristotlePagaltzis 24
25 <pre>
4 AristotlePagaltzis 26 env -u LANG ssh $ilo
3 JohnMcPherson 27 </pre>
4 AristotlePagaltzis 28
29 Note that "<tt>LANG= ssh -v $server</tt>" only sets the variable to the empty string which your [SSH] client will still send, which is enough to confuse iLO:
30
3 JohnMcPherson 31 <pre>
32 debug1: Sending env LANG =
2 AristotlePagaltzis 33 </pre>