Category Archives: Solaris

How to reset/recover Integrated Lights Out Manager (ILOM) password

Posted by S.Aziz on

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

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

Notes:
– 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.

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

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

-> set /SP/users/root password
Enter new password: ********
Enter new password again: ********

6. Type “exit” to leave default login
7. try login with your new root password

—————-

Update for The “Physical Presence” button locations by server:
locate_button

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

SPARC_T4_1_rear_zoom

NOTES
– 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 the 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

If you have MOS access, read more on doc : 1509660.1

Oracle Support Document 1509660.1 (How to locate the “Physical Presence” button on SPARC T3-x, T4-x, T5-x, T7-x, S7-x Servers)

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1509660.1

 

Advertisement

How to bypass and reset the ALOM password for Sun V-Series and Netra Series

Posted by S.Aziz on

How to bypass and reset the ALOM password on Sun Fire V125/V210/V215/V240/V245/V250/V440/V445 and Sun Netra 210/240/440 Servers.
Use scadm utility to reset the admin password:
# cd /usr/bin/cd /usr/platform/`uname -i`/sbin
# ./scadm userpassword admin

Return to the ALOM login prompt
Now, login into the “admin” account using the new password

Update:

If the SCADM not available, download the RSC software from MOS:

RSC Software Download (steps to download the latest RSC software):
1. Login to MOS and select “Patches and Updates Tab”
2. In “Patch Search” on the Top right panel, Click on “Product or Family (Advanced Search)”
3. In the “Product Is” pull-down select “Sun remote System Control”??
4. In the next pull down “Release is” select the RSC version (2.2.2 or 2.2.3).
5. Select OS and click “Search” (will get a list with RSC releases & patches)
6. Select the desired RSC Release (packages) or patch
7. Click Download on the Right

The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are no differences: p10264452_223_SOLARIS64.zip (p10264451_223_SOLARIS.zip)

Install the software as you would any Package with pkgadd.

Command syntax is same:
#/usr/platform/`uname -i`/rsc/rscadm userpassword admin
[To reconfigure the card run the command:
# usr/platform/`uname -i`/rsc/rsc-config

[If you had installed the software before and believe the card is configured check the setup:
# usr/platform/`uname -i`/rsc/rscadm show

How to reset the ILOM root password back to the default ‘changeme’ using ipmitool

Posted by S.Aziz on

If the root password on the ILOM is currently unknown, but you have root access to the O/S installed, you can change the ILOM password back to the default “changeme”.

Follow below steps:
# which ipmitool
/usr/sbin/ipmitool

# /usr/sbin/ipmitool -V
ipmitool version 1.8.8

# /usr/sbin/ipmitool user set password 0x02 changeme

[or you can also use the raw format:
# /usr/sbin/ipmitool raw 0x06 0x47 0x02 0x02 0x63 0x68 0x61 0x6e 0x67 0x65 0x6d 0x65 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

There will be no confirmation after running the ipmitool command, however the ILOM root password will be changed to changeme.

Solaris UADMIN commands

Posted by S.Aziz on

uadmin 2 0
sync the filesystems and drops system to ok prompt
uadmin 2 1
sync the filesystems and reboots to multi-user mode
uadmin 2 2
sync the filesystems and reboots interactively
uadmin 2 3
sync the filesystems and reboots to single-user mode
uadmin 2 6
sync the filesystems and powers off the system
uadmin 1 0
do not sync filesystems and drops system to ok prompt
uadmin 1 1
do not sync filesystems and reboots to multi-user mode
uadmin 1 2
do not sync filesystems and reboots interactively
uadmin 1 3
do not sync filesystems and reboots to single-user mode
uadmin 1 6
do not sync filesystems and powers off the system

 

How To Boot Solaris Cluster into Non-Cluster Mode

Posted by S.Aziz on

Shut down the specific Global Cluster

# clnode evacuate <nodename>
# cluster shutdown -g0 -y

 

For SPARC, drop system to OK Prompt, then type ‘boot -xs’.

ok> boot -xs

For X86:
– In the GRUB menu, use the arrow keys to select the appropriate Solaris entry and type e to edit its commands.
GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+————————————————————————-+
| Solaris 10 /sol_10_x86                                                  |
| Solaris failsafe                                                        |
|                                                                         |
+————————————————————————-+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, ‘e’ to edit the
commands before booting, or ‘c’ for a command-line.

– In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.
The GRUB boot parameters screen appears similar to the following:
GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
+———————————————————————-+
| root (hd0,0,a)                                                       |
| kernel /platform/i86pc/multiboot                                     |
| module /platform/i86pc/boot_archive                                  |
+———————————————————————-+
Use the ^ and v keys to select which entry is highlighted.
Press ‘b’ to boot, ‘e’ to edit the selected command in the
boot sequence, ‘c’ for a command-line, ‘o’ to open a new line
after (‘O’ for before) the selected line, ‘d’ to remove the
selected line, or escape to go back to the main menu.

-Add -x to the command to specify system boot in noncluster mode.
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ESC at any time exits. ]

grub edit> kernel /platform/i86pc/multiboot -x

-Press the Enter key to accept the change and return to the boot parameters screen.
The screen displays the edited command.
GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
+———————————————————————-+
| root (hd0,0,a)                                                       |
| kernel /platform/i86pc/multiboot -x                                  |
| module /platform/i86pc/boot_archive                                  |
+———————————————————————-+
Use the ^ and v keys to select which entry is highlighted.
Press ‘b’ to boot, ‘e’ to edit the selected command in the
boot sequence, ‘c’ for a command-line, ‘o’ to open a new line
after (‘O’ for before) the selected line, ‘d’ to remove the
selected line, or escape to go back to the main menu.-

-Type b to boot the node into noncluster mode.

How to reset RSC password

Posted by S.Aziz on

If you forgot the RSC password for V480, V880, V490, and V890 or other old legacy Sun machines, here are the procedure to reset the password. Requirement: SUNWrsc package

If you dont hv the package, please download the latest package from My Oracle Support:

  1. login to support.oracle.com
  2. click on “Patches & Updates” in the top menu
  3. in the search window (located on the right) click “Product or Family (Advanced)”
  4. in the updated search window type “Sun Remote” in the “Product” box, then select “Sun Remote System Control”
  5. Click the “Release” box (which says “Select up to 10”, in that box click “Sun Remote System Control” and then select the version “Sun Remote System Control 2.2.3”.
  6. In the new window you can now download RSC 2.2.3 (called p10264451_223.zip) by marking it and clicking “download”.

[reset RSC password:

Login with root privilege, install the package, then run rscadm command.

Prefix >> #/usr/platform/<platform>/rsc/rscadm userpassword <username>

[example for v890:
# /usr/platform/SUNW,Sun-Fire-V890/rsc/rscadm userpassword admin
Password:
Re-enter Password:

You can also reset the whole configuration by running “rsc-config” command.

Update:

If the SCADM not available, download the RSC software from MOS:

RSC Software Download (steps to download the latest RSC software):
1. Login to MOS and select “Patches and Updates Tab”
2. In “Patch Search” on the Top right panel, Click on “Product or Family (Advanced Search)”
3. In the “Product Is” pull-down select “Sun remote System Control”??
4. In the next pull down “Release is” select the RSC version (2.2.2 or 2.2.3).
5. Select OS and click “Search” (will get a list with RSC releases & patches)
6. Select the desired RSC Release (packages) or patch
7. Click Download on the Right

The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are no differences: p10264452_223_SOLARIS64.zip (p10264451_223_SOLARIS.zip)

Install the software as you would any Package with pkgadd.

Command syntax is same:
#/usr/platform/`uname -i`/rsc/rscadm userpassword admin
[To reconfigure the card run the command:
# usr/platform/`uname -i`/rsc/rsc-config

[If you had installed the software before and believe the card is configured check the setup:
# usr/platform/`uname -i`/rsc/rscadm show

How to clear fmadm log or FMA faults log

Posted by S.Aziz on

Here are the step by step of clearing the FMA faults on most of Oracle/Sun server. Work perfectly on Solaris 10:

Clear fmadm log, Example :
———————————-
For each fault listed in the ‘fmadm faulty’ run:
# fmadm repair <uuid>   (OR if the components are listed instead, e.g.:)
# fmadm repair 568a9180-7308-4535-92e6-a7c17ef1bfef

[Clear ereports and resource cache:
# cd /var/fm/fmd
# rm e* f* c*/eft/* r*/*

[Clearing out FMA files with no reboot needed:
svcadm disable -s svc:/system/fmd:default
cd /var/fm/fmd
find /var/fm/fmd -type f -exec ls {} \;
find /var/fm/fmd -type f -exec rm {} \;
svcadm enable svc:/system/fmd:default

[Reset the fmd serd modules:
# fmadm reset cpumem-diagnosis
# fmadm reset cpumem-retire
# fmadm reset eft
# fmadm reset io-retire

Host Power-On Failed: System Power OK, Open Boot not responding

Posted by S.Aziz on

I faced this issue while troubleshooting disk issue on Sun Fire V440.

The disk has intermittently undetected from host, tried to upgrade the OBP firmware from 4.13 to 4.30, found the amber light with below error messages:

“Host Power-On Failed: System Power OK, Open Boot not responding”

————–
sc> poweron
SC Alert: Host System has Reset
sc>
SC Alert: Host Power-On Failed: System Power OK, Open Boot not responding
sc>
SC Alert: Host System has Reset
————-

found related KB while searching on MOS:

“On V440/N440 2P systems with OBP 4.22.19 firmware and ALOM firmware 1.5.4 may encounter a host power on failure. (Doc ID 1000080.1)”

Root Cause

The root cause was determined to be the OBP probe timeout value of 2.5 seconds set in ALOM 1.5.4.

Deviation WO_35484 was issued to Celestica (CMX) to rework V440/N440 systems by loading ALOM 1.6.3 FW.

 

Document 1000080.1 can be found at:

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1000080.1

 

So, there is a bug on current ALOM. the OBP firmware is upgraded to the latest already, now what I need to do is to upgrade the ALOM firmware. Patch id/name is 10263984

  • Install patch ID 10263984, its contains 2 file. For V440, use “ALOM_1.6.10_fw_hw0.tar.gz”.
  • Copy and extract file “ALOM_1.6.10_fw_hw0.tar.gz” to “/usr/platform/SUNW,Sun-Fire-V440/lib/images” directory.
  • Then, run command: “scadm download boot alombootfw”

bash-3.00# pwd
/usr/platform/SUNW,Sun-Fire-V440/lib/images
bash-3.00# gzcat ALOM_1.6.10_fw_hw0.tar.gz | tar xf –
bash-3.00# /usr/platform/`uname -i`/sbin/scadm download boot alombootfw
……………….. (100%)
Download completed successfully
Please wait for verification
..
Complete
bash-3.00# /usr/platform/`uname -i`/sbin/scadm download alommainfw
…………………………………. (6%)
…………………………………. (12%)
…………………………………. (18%)
…………………………………. (25%)
…………………………………. (31%)
…………………………………. (37%)
…………………………………. (44%)
…………………………………. (50%)
…………………………………. (56%)
…………………………………. (63%)
…………………………………. (69%)
…………………………………. (75%)
…………………………………. (81%)
…………………………………. (88%)
…………………………………. (94%)
……………………………. (100%)
Download completed successfully
Please wait for verification
……
Complete
bash-3.00# exit

Reboot the machine, then you will see the amber light will gone.

Creating a Jumpstart Server from ISO images

Posted by S.Aziz on

What is Jumpstart ? Jumpstart is a computer network installation tool set used by the Solaris OS. On this post, you will find easy step to perform Jumpstart installation from ISO Solaris OS images.

here are the step-by-step:

  • first of all, you need to upload Solaris ISO image to server that will used as Jumpstart server. In this example, my ISO images is “sol-10-u8-ga-sparc-dvd.iso” and I uploaded already to root home directory (/).
  • Add your client IP address & hostname to “/etc/hosts”, also the hostname and mac address to “/etc/ethers”.

if your client is Sparc, then you can find the mac address by running “banner” command from OK prompt. For x86, the mac address can be found on BIOS.

# more /etc/hosts
::1     localhost
127.0.0.1       localhost
10.32.16.1      solaris10 solaris10. loghost
192.168.1.2    client1
192.168.1.3    client2
192.168.1.4    client3

# more /etc/ethers
0:0:be:a5:1a:9e client1
0:0:be:a5:1a:9f client2
0:0:be:a5:1a:a0 client3

  • mount ISO images using “lofiadm” command to “/mnt” directory:

# lofiadm -a /sol-10-u8-ga-sparc-dvd.iso /dev/lofi/1
# lofiadm
Block Device             File
/dev/lofi/1              /sol-10-u8-ga-sparc-dvd.iso
# mount -F hsfs -o ro /dev/lofi/1 /mnt

  • Check the “/mnt” directory, the jumpstart scripts are located at “/Solaris_10/Tools/” directory:

# cd /mnt/Solaris_10/Tools/
# ls
add_install_client    dial                  rm_install_client
Boot                  Installers            setup_install_server

  • If you don’t hv enough disk space, then you can run “add_install_client” script directly:

the format is “add_install_client <hostname> <platform>”

#./add_install_client client1 sun4u
saving original /etc/dfs/dfstab in /etc/dfs/dfstab.orig
Adding “share -F nfs -o ro,anon=0 /mnt” to /etc/dfs/dfstab
making /tftpboot
enabling tftp in /etc/inetd.conf
starting rarpd
starting bootparamd
starting nfsd’s
starting nfs mountd
updating /etc/bootparams
copying boot file to /tftpboot/inetboot.SUN4U.Solaris_10-1
#

NOTE: If you want to copy all or part of the install DVD onto a system to set it up as a long term install server with the install media available on local disk, then you can run “setup_install_server” script.

FORMAT: setup_install_server <destination_dir>.

  • Check “/etc/bootparams”. The bootparams file contains a list of client  entries  that diskless  clients  use for booting. Make sure your client listed in there..
  • Configure Client to boot from Network. for Sparc, run “boot net – install” from OK Prompt. For X86 configure BIOS to boot from Network.
  • Follow the installation procedure till finish..

NOTE For X86/i386pc:

  1. You need to configure DHCP macro on Jumpstart server, run “/usr/sadm/admin/bin/dhcpmgr” from X Windows / GUI, then click EDIT > NETWORK WIZARD.
  2. put “i386pc” as your platform while running add_install_client , exp:

./add_install_client -d -e 0:0:be:a5:1a:9e -s 192.168.1.1:/mnt i86pc

NetBackup Support Utility (NBSU)

Posted by S.Aziz on

Did you know what is NBSU or NetBackup Support Utility? this is a great tools to gather diagnostic information in where Netbackup is installed and running. Its replaced what is known as “nbsupport” in previous versions.

“The NetBackup Support Utility (NBSU) is a Symantec utility used to gather diagnostic information about the system on which the utility is run. By default, NBSU gathers appropriate diagnostic information based on the Operating System and NetBackup environment.  With the availability of many command line options, the diagnostic information gathered can be tuned as desired”.

Actually, if you install Netbackup on Solaris, you can also run the Explorer command using an option “nbu_extended” like this:

/opt/SUNWexplo/bin/explorer -w default,nbu_extended

with “nbu_extended” option, the Explorer will collects Extended NetBackup information. Its not only gather the log, it will also run a few commands, collect the directories and more. see here to know what Explorer with nbu_extended do later on your systems.

Back to NBSU, for more detail about this great tools and to understand well on how to run nbsu commands, please click the link below:

DOCUMENTATION: What is the nbsupport utility and where can it be found?
http://support.veritas.com/docs/264785

DOCUMENTATION AND DOWNLOAD: NetBackup Support Utility (NBSU) Usage and Examples for 6.x. NBSU was released with 6.5, 6.0 MP6, and 5.1 MP7, and replaces what is known as “nbsupport” in previous versions.
http://support.veritas.com/docs/323434