Fixing ILOM command errors
I have recently seen a number of our systems onsite where access to the ILOM is none responsive via the web interface and ssh
timeout or painfully sluggish, and at times it appears the console is simply in a hung state. When trying to reboot the SP I get the following error:
$ ssh root@10.1.1.10 Password: Sun(TM) Integrated Lights Out Manager Version 2.0.2.6 Copyright 2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Warning: password is set to factory default.-> reset /SP Are you sure you want to reset /SP (y/n)? y Performing hard reset on /SP failed reset: No such inventory -> exit Connection to 10.1.1.10 closed.
Or when you try to reset the ILOM password or any other command, you get the error:
Set: No such object value
To resolve either of these issues log onto the ILOM as user sunservice
and reboot the ILOM with the reboot
command.
$ ssh sunservice@10.1.1.10 Using keyboard-interactive authentication. Password: Copyright 2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: The “sunservice” account is provided solely to allow Sun Services to perform diagnosis and recovery tasks. Customer use of the “sunservice” account may interfere with the correct operation of ILOM and is not supported other than to perform recovery procedures as documented by Sun Microsystems. Normal ILOM operations should always be performed using the root account. Further usage of the “sunservice” account implies your agreement with these terms. [(flash)root@SUNSP001:~]# /sbin/reboot Read from remote host 10.1.1.10: Connection reset by peer Connection to 10.1.1.10 closed.
ILOM v3
The sunservice
account does not exist anymore with ILOM v3.0 and my colleagues in engineering suggest that you should upgrade to the latest ILOM firmware. But you could try the following:
-> ilomconfig modify network --state=disabled -> ilomconfig modify network --state=enabled
You may need to install the Oracle hardware management pack
Brute force & ignorance
The following steps could be used as a last resort:
- Shutdown the Solaris OS system:
init 5
- at the ILOM prompt, type:
stop /SYS
- Once the server has powered off, type:
reset /SP