How to reset/recover Integrated Lights Out Manager (ILOM) password on Sun SPARC T4-2

Tekmart Infrastructure SecurityTeam/ August 10, 2022/ Batting for Tech in the Covid-19 Times, Best practices for data center operations, Data center facilities, Data Center Hardware, Data Centre Hardware Equipment Technical Resources, Data centre networking, Data Centre Servers, How-Tos and Other Useful Tips and Tricks, Infrastructure in the Data Centre, Sun SPARC Hardware, Tekmart Enterprise Hardware Tips

Reading Time-approximately: 2 minutes

System administrators can recover the preconfigured Oracle ILOM local root account or the password for the local root account by using the preconfigured Oracle ILOM default password.

By Tekmart Africa Enterprise Support

To recover the root account password you need a local serial management port (SER MGT) connection to Oracle ILOM. In addition, if the Physical Presence State is enabled (the default) in Oracle ILOM, you must prove that you are physically present at the server.

To recover the lost root account password, perform these steps:

The default user and password of ILOM is “root/changeme”, but if you have changed the password already and due for some reason you forgot the password, here are the step by step to recover the ILOM password.

First of all, try to change the password with ipmitool, but if its still doesn’t work, try below step:

Caveat:
– You must be physically present at the server to perform this procedure.
– This procedure uses the default user account to enable you to recover a lost password or to re-create the root user account.
– You cannot change or delete the default user account.

1. Connect to ILOM via serial console and log in using the default user account.
SUNSP-xxxxxxxx login: default
Press and release the physical presence button.
Press return when this is completed…

2. Prove physical presence at your server.
Press and release the physical presence button (we used a pin in our case)

The Physical Presence button on the Sun SPARC Enterprise T5xxx servers and X-Series is the Locator button:

But, for Sparc T3/T4 model, the physical presence are on rear side, except for T3-1b/T4-1b:
SPARC T3-1/T4-1: (rear) pin-hole to the left of the USB ports
SPARC T3-2/T4-2: (rear) pin-hole to the left of NET0
SPARC T3-4/T4-4: (rear) to the right of OK LED, above the USB port
SPARC T3-1b/T4-1b: (front) Locate button/Physical Presence (White LED)

3. Return to your serial console and press Enter.

You will be prompted for a password.

4. Type the password for the default user account: defaultpassword (please note the lower case in the password characters)

5. Reset the account password or re-create the root account.

-> set /SP/users/root password
Enter new password: ******** (take great care here, the password characters will not be revealed as you type, so you should be double sure of the password)
Enter new password again: ********

6. Type “exit” to leave default login
7. You should now be able to login with your new root password

Physical Presence for SPARC T4-1 : rear, pin/hole between net3 and usb0 (red circle)

Also note:-
– T7-x, S7-x and all platforms forward should use the Locator button (front/rear) as the Physical Presence switch
– To perform some procedures documented in the Oracle ILOM core documentation, you must create a serial connection to the server and activate the Physical Presence switch on the server. For information about creating a serial connection, refer to the installation guide for your particular server.
– If the physical presence/locator button is not working and/or can not be located, then as temporary workaround the physical presence check can be disabled:
– -> show /SP check_physical_presence
– -> set /SP check_physical_presence=false
– -> show /SP check_physical_presence
and it can be later enabled
– -> show /SP check_physical_presence
– -> set /SP check_physical_presence=true
– -> show /SP check_physical_presence
– For more information look at the documents below:
– T Series Server Documentation
– Oracle Integrated Lights Out Manager (ILOM) 3.x Documentation

Share this Post