Showing posts with label openboot. Show all posts
Showing posts with label openboot. Show all posts

Friday, December 15, 2023

Oracle Refreshed SPARC T8 Model

 

Oracle Refreshed SPARC T8 Model

Abstract:

In September 2017, Oracle released their flagship M8 RISC CPU, with T8 platforms based upon it! The S5 Core was an amazing accomplishment, 4 instructions per clock cycle, screaming at 5 GHz. Fujitsu simultaneously released their SPARC64 XII CPU, with SPARC M12 Platforms. Solaris 11.3 was supposed to become Solaris 12, but instead was branded as Solaris 11.4 to encourage continuity. The M8+ processors listed on the now unpublished SPARC/Solaris Roadmap, were supposed to be released in 2020. Fujitsu released a roadmap of a SPARC memory increase of 1.5% in 2021, and Fujitsu came out with new memory risers to expand memory by 150%. Oracle matched & passed Fujitsu in 2022/2023 transition.

Recent M8 Platform Additions

The SPARC M8 Platforms, like the T8-2 systems, were given new phenomenal upgrades:

  • Double Memory with memory DIMM upgrades from 64 GB to 128 GB 
  • Double SAN Storage Throughput from 16 GB to 32 GB HBA Cards
  • Quadruple Network Speed Throughput from 25 GBit to 100 GBit NIC Cards
  • Live Upgrade for Firmware
  • Better Live Migration

The expense of the larger DIMMS is dramatic. Let's compare the rough costs.

  • 1TB T8-2 Chassis /w 32GB DIMM's can be used as a baseline.
  • 2TB T8-2 Chassis /w 64GB DIMM's is similar to buying 2x 1TB T8-2 /w 32GB DIMM's. 
  • 4TB T8-2 Chassis /w 128GB DIMM's is similar to buying 4x 1TB T8-2's /w 32GB DIMM's.

The cost of the new increase capacity is not for the faint of heart.

The 2022/2023 T8-2 Component Refresh

Trade rag coverage on SPARC hardware & software updates has been anemic, at best.
How could we see the future, when trade rags were negligent in their reporting?
Oracle released SPARC T8 features between end-2022 to start-2023, forecast in bug notes.

NOV 2022 - Firmware 9.10.5

Oracle worked on 128 GB DIMM's & 6.8TB Flash F640 v4 NVMe PCIe Card (Aura 10 AIC)
  •     33752815 NVME/T_IN read bad value 96 with Aura10-SFF Intel in T8 and S7
  •     33627980 prtfru displays incorrect DIMM capacity for 128GB DIMMs

MAR 2022 - Firmware 9.10.4.a

Feature Request for Intel NVMe Solid State Drive Assembly Aura10 and improved live migration 

  •    33691051 Aura10 SFF support for SPARC
  •    33741127 Add a subguest API minor version for migration-class2 bugfix presence

OCT 2021 - Firmware 9.10.3

Improvements to firmware patching, Ethernet Cards, Memory, and improved live migration.

  •    33216275 Enable live patching in Hypervisor 1.20.6
  •    33171094 Add card identification support for Intel Ethernet Server Adapter I210-T1 OEM Gen to ILOM
  •    33005242 Add ereport.hc.dev_info for memory risers
  •    32978497 T8-2 YMR VMEM ZL9025 ASCR_CONFIG change to match T8-1 value
  •    32929538 Increase maximum chunks to account for larger dimms
  •    32925557 Add Oracle ConnectX-6 Dx EN , 2x100GbE, Dual-port QSFP, Crypto and Secure Boot FW ILOM support (Mellanox ConnectX NIC - Mellanox 25G/100GbE Adapter) (NVIDIA ConnectX-6 Dx Network Adapters) (NVIDIA Connect X-6 Dx Datasheet: ConnectX-6 Dx provides up to two ports of 100Gb/s or a single port of 200Gb/s Ethernet connectivity and is powered by 50Gb/s (PAM4) or 25/10 Gb/s (NRZ) SerDes technology.)
  •    32920850 HV support for a Tahoe+ migration class
  •    32838122 Additional changes needed for live patching of 32625647/31561348 (live firmware patching)

JUN 2021 - Firmware 9.10.2

Feature request for Intel NVMe Solid State Drive 6.4TB Flash Accelerator F640 v3 NVMe PCIe Card (Aura 9 AIC), additional DRAM Support, and Network Cards

  • 33691051 Aura10 SFF support for SPARC
  • 32074098 Add Aura9 SFF support to SPARC platforms
  • 31365759 [ILOM] "hwdiag pci info" does not show Aura8 SFF Subsystem Vendor ID, Subsystem Device ID, Part Number and Description
  • 32385998 Aura 9 SFF fail post in some systems
  • 32372784 Add timing data for more DRAM types
  • 31447119 Device Monitor: Add support for CX-5 OCP,CX-5 2x100G OCP, CX-6 Dx, and CX-6 Dx 50G, and CX-6 Dx 50G Bifurcated cards
  • 31365759 [ILOM]"hwdiag pci info" does not show Aura8 SFF Subsystem Vendor ID, Subsystem Device ID, Part Number and Description

APR 2021 - Firmware 9.10.1.a (available in 9.10.1.c)

Feature request for Intel NVMe Solid State Drive 6.4TB Flash Accelerator F640 v3 NVMe PCIe Card (Aura 9 AIC) and Live Firmware Patching

  • 31792974 Updating Aura9 Descriptions and adding Samsung v2
  • 32182811 Support multiple tcp connections on SSH-DCA port (security scanners)
  • 32059898 Enable live patching in Hypervisor 1.20.5

AUG 2020- Firmware 9.10.0.a

Feature request for Intel NVMe Solid State Drive 6.4TB Flash Accelerator F640 v3 NVMe PCIe Card (Aura 9 AIC), Intel NVMe Solid State Drive 6.4TB Flash Accelerator F640 v2 NVMe PCIe Card (Aura 8 AIC), Intel NVMe Solid State Drive 6.4TB Flash Accelerator F640 v1 NVMe PCIe Card (Aura 7 AIC), 100 GbE Support, 128 GB DIMM, and Live Firmware Patching

  • 31225789 Bug fix for Intel NVMe Solid State Drive Assembly Aura9
  • 31388207 After reset /System, mctp_drive failed on Aura8 SFF
  • 31225789 Device Monitor: Add support for Intel prototype Aura9
  • 31218973 Failed to access Aura9 SSDs via MCTP/SMBus on E2-2C
  • 31190919 add aura9/7 aic to i2c test
  • 31181415 Enable live patching in Hypervisor 1.20.4
  • 31181349 Device Monitor: Add support for Intel/Samsung Aura9
  • 30898834 ILOM change request to support Aura9 SFF from Intel/Samsung and AIC from Intel
  • 31440160 Add CX-6 Dx 50G iLOM support
  • 31404646 Add CX-6 Dx 2x100G iLOM support
  • 31388207 After reset /System, mctp_drive failed on Aura8 SFF
  • 31388020 Add CX-5 2x100G OCP NIC support to iLOM
  • 30793129 libfru DDR4 (SPD_128RW_FORMAT) CRC protection is ineffective
  • 30766834 ILOM is not identifying the part number and description of the Cx5 card
  • 30738307 DDR4 (SPD_RW128_FORMAT) SPD_Fault_Data Rrecord re-initialized on SP reboot.

 

Conclusion:

Oracle continues to  refresh their SPARC S7 & T8 lines, with Memory & Network capacity, OS Capabilities, and Firmware Capabilities. We can see from the bug trail that it takes A LONG TIME for Oracle's development team to push features to fruition, about 2 years, but updates are still coming. It is great to see one of the fastest platforms on the planet, dating back to 2017, continuing to get hardware and software updates. More is coming.

Monday, February 27, 2023

How Do I Save the LDoms Configuration under Solaris?

 

 Abstract:

Under SPARC Logical Domains, the Hypervisor is actually running in the firmware of the chassis, where the Control Domain sends commands to partition the hardware underneath the OS's. The hypervisor and all settings are completely in memory... which means if there is a power outage, all virtualization configuration can be lost. The ILOM has onboard storage, to hold the LDoms configuration, when saved, and the hypervisor in the firmware is smart enough to request the configuration from the ILOM on boot, and then simultaneously boot all Logical Domains (including the Control Domain.)

List LDom Configurations

To list all Logical Domain Configurations, which were stored to the ILOM:

sun1824-cd/root# ldm list-spconfig
factory-default
@post-migration [current]
default-config
20190301
20191002
20211014
20220908

Note: in the above example, the "@post-migration" means the configuration was saved the last time someone executed a live migration onto or off of this platform, with the "-s" flag for "save config".

Save Logical Domain Configuration

To save a copy of the LDom configuration:

sun1824-cd/root# ldm add-spconfig `date +%Y%m%d`
sun1824-cd/root#

List Saved Logical Domain Configurations

The newly saved logical domain configuration  should show as the Year, Month, Day combination

sun1824-cd/root# ldm list-spconfig
factory-default
@post-migration
default-config
20190301
20191002
20211014
20220908
20230218 [current]
sun1824-cd/root#



 

Monday, November 14, 2022

Installing a ISO from ILOM 4.0.3+ using SSH

Installing a ISO from ILOM 4.0.3+ using SSH

Abstract:

The SPARC platform have long come with various Lights Out Management (LOM) capabilities, to access the hardware, and provide for access to the OS from underneath, when there is a hardware issue. A more advanced system called Integrated Lights Out Management (ILOM) was later created. With ILOM 4.0.3, a feature was created to allow for the boot from a remove ISO via SSH!

Where to get ISO:

The easiest place to get the most recent version of Solaris, such as the Common Build Edition

https://www.oracle.com/solaris/solaris11/downloads/solaris-downloads.html

Various ISO's are available from Oracle for Solaris:

Where to download Oracle Solaris ISO images and Update Releases (Doc ID 1277964.1) 
https://support.oracle.com/epmos/faces/DocumentDisplay?id=1277964.1

What to do from ILOM:

Copy ISO's to a local directory on a server

a.b.c.d/user$ ls -l /export/home/user/*iso
a.b.c.d/user$ ls -al /u000/P2V/iso/*iso
-rw-r--r--   1 user root   2314731520 May 12  2016 /export/home/user/sol-10-u11-ga-sparc-dvd.iso
-rw-r--r--   1 user root     867020800 May 13  2016 /export/home/user/sol-11_3-text-sparc.iso
-rw-r--r--   1 user root   1018736640 Apr 23  2019 /export/home/user/sol-11_4-text-sparc.iso
-rw-r--r--   1 user root     551464960 Oct 20  2011 /export/home/user/sol-11-1111-text-sparc.iso

Make sure there is connectivity from the ILOM to the Server hosting the ISO

-> set /SP/network/test ping=a.b.c.d
Ping of
a.b.c.d succeeded

Set the ILOM Host Storage Device to Remote

-> set /SP/services/kvms/host_storage_device/ mode=remote

Set the username, password, and ISO location

-> cd /SP/services/kvms/host_storage_device/remote

-> set username=user
-> set password=password
-> set server_URI=sshfs://a.b.c.d:/export/home/user/sol-11_4-text-sparc.iso

/SP/services/kvms/host_storage_device=remote
Targets:
Properties:
password = *****
server_URI = sshfs://a.b.c.d:/export/home/user/sol-11_4-text-sparc.iso
username = user

Review Values

-> show /SP/services/kvms/host_storage_device/

/SP/services/kvms/host_storage_device

Targets:
remote

Properties:
mode = remote
status = operational 

Stop Automatic Boot on Host

-> set /HOST/bootmode script="setenv auto-boot? false"

Mount & Boot the Remote ISO

-> start /SP/console -script 

{ok} reset-all
{ok} devalias
...
rcdrom

{ok} ok boot rcdrom

Boot device: /pci@311/pci@1/usb@0/storage@1/disk@0 File and args:
SunOS Release 5.11 Version 11.4.0.15.0 64-bit
Copyright (c) 1983, 2018, Oracle and/or its affiliates. All rights reserved.
Remounting root read/write
Probing for device nodes ...
Preparing image for use
NOTICE: mount: not a UFS magic number (0x0)
NOTICE: mount: not a UFS magic number (0x0)
Done mounting image
USB keyboard
1. Arabic 15. Korean
2. Belgian 16. Latin-American
3. Brazilian 17. Norwegian
4. Canadian-Bilingual 18. Portuguese
5. Canadian-French 19. Russian
6. Danish 20. Spanish
7. Dutch 21. Swedish
8. Dvorak 22. Swiss-French
9. Finnish 23. Swiss-German
10. French 24. Traditional-Chinese
11. German 25. TurkishQ
12. Italian 26. UK-English
13. Japanese-type6 27. US-English
14. Japanese

To select the keyboard layout, enter a number [default 27]:

Additional Information

A good note on this process is available for people with Oracle Support:
How to Install/Re-image a T5-x, S7, T7-x, T8-x, M7-x, or M8-x System Using the sshfs Protocol (Doc ID 2817892.1)
https://support.oracle.com/epmos/faces/DocumentDisplay?id=2817892.1


Monday, June 7, 2021

SPARC: OpenBoot - Disable Auto-Boot?

 

SPARC: OpenBoot - Disable Auto-Boot?

Abstract:

SPARC based platform have a level of firmware between the chassis hardware and the loaded OS called OpenBoot, The IEEE created a standard based upon it, IEEE 1275-1994, and it was called OpenFirmware. Sun Microsystem's OpenBoot was released as Open Source in 2006 under a BSD license, and other vendor implementations were also released. The persistent settings for OpenBoot are held in the environment, as well as defaults, and changes can be made to the EEPROM. The Auto-Boot? environment value is one typical value commonly adusted.

[Sun Microsystems T4-2 Chassis]

Achieve Console

Console can be achieved on a typical rack mount system via TCP/IP connection to the ILOM, with a command to grab the console to the OK prompt (assuming the autoboot flag is disabled.)

sun9876/root# ssh root@T4-2-ilom
Password:

Oracle(R) Integrated Lights Out Manager
Version 3.2.6.8 r128095
Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.
Warning: HTTPS certificate is set to factory default.
Hostname: ORACLESP-1207BDY086

->  

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.

{0} ok

The Environment

The environment consist of a series of label-value pairs. Those labels define the characteristics by which the behavior of the chassis can be modified during any changes.

Show OpenBoot Environment Values & Defaults

The printenv command shows a copy of all label-value pairs, as well as defaults.

{0} ok printenv
Variable Name           Value                          Default Value

ttya-rts-dtr-off        false                          false
ttya-ignore-cd          true                           true
keyboard-layout         US-English
reboot-command
security-mode           none                           No default
security-password                                      No default
security-#badlogins     0                              No default
verbosity               min                            min
diag-switch?            false                          false
local-mac-address?      true                           true
fcode-debug?            false                          false
scsi-initiator-id       7                              7
oem-logo                                               No default
oem-logo?               false                          false
oem-banner                                             No default
oem-banner?             false                          false
ansi-terminal?          true                           true
screen-#columns         80                             80
screen-#rows            34                             34
ttya-mode               9600,8,n,1,-                   9600,8,n,1,-
output-device           virtual-console                virtual-console
input-device            virtual-console                virtual-console
auto-boot-on-error?     false                          false
load-base               16384                          16384
auto-boot?              true                           true
os-root-device
network-boot-arguments
boot-command            boot                           boot
boot-file
boot-device             /pci@700/pci@1/pci@0/pci ...   disk net
multipath-boot?         false                          false
boot-device-index       0                              0
use-nvramrc?            false                          false
nvramrc                 ." ChassisSerialNumber 1 ...
error-reset-recovery    boot                           boot
{0} ok 

Set an AutoBoot Environment

The autoboot flag, in the above example, is currently enabled, which is also the default value.
This can be disabled, for the purpose of loading a new OS after a fresh reboot.

{0} ok printenv auto-boot?
auto-boot? =            true

{0} ok setenv auto-boot? false
auto-boot? =            false

{0} ok printenv auto-boot?
auto-boot? =            false

Conclusion:

Environment Label-Value pairs in OpenBoot drive the behavior of the firmware. This value can be set to true, to force boot on chassis power up, or to leave the OS at the "ok" prompt on power up. This is definitively helpful in an environment where a failure may take a chassis down unexpectedly, VM's were brought up on an alternate chassis, and repair of the failued chassis environment is not desirable to bring up the OS formerly running on the failed chassis until an orderly transition can be enabled.

Monday, May 31, 2021

How to get to an OK prompt on a SPARC

[Logo of Sun Microsystems]

How to Get to an OK prompt on a SPARC

Abstract:

From the beginning of reasonable UNIX Workstation Time, the Workstation typically had a physical hardware layer, a firmware layer, and an OS layer. The Firmware layer used by UNIX workstations was Open-Sourced by Sun Microsystems as OpenBoot, given to the market for vendors like IBM, Apple, etc. The FORTH based environment was called OpenFirmware by the IEEE. One such feature is to boot the operating system directly, from a pre-selected disk, in a pre-selected order. When booting from a different boot environment, like a USB stick, this can be stopped. All of this can be achieved from the OpenBoot "OK" prompt.

[Sun Microsystems Type 5 Keyboard, courtesy Deskthority]

From a Physical Console

If you are lucky enough to have a real SUN Keyboard, Video Monitor, and Mouse (KVM), breaking out to OpenBoot is easily achieved by using the following key sequence "[L1] [A]". The "[L1]" key may be labeled "Stop" on some newer keyboards, but the position is the same, so the simultaneous key sequence would be "[Stop][A]".

{0} ok

From an ILOM Console

If one is not lucky enough to have a physical console, it can be accomplished from an ILOM Console. 

T5120/user$ ssh root@SUNT4-2-ilom
Password:

Oracle(R) Integrated Lights Out Manager
Version 3.2.6.8 r128095
Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.
Warning: HTTPS certificate is set to factory default.
Hostname: ORACLESP-1207BDY07F
-> 

Go Directly to OK from ILOM Console

If the system AutoBoot is not configured, the OK prompt will appear on a powered up chassis console

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

{0} ok

Go to OK from ILOM Console & Booted OS

If the system AutoBoot is configured, the OS prompt will appear on a powered up chassis console

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
 
sunt4-2 console login: root
password: ****
sunt4-2/root# cd / ; sync ; init 0

{0} ok

Go to OK from ILOM Console & Booted OS without root

If the system AutoBoot is configured, the OS prompt will appear on a powered up chassis console.
If there is no root password for the system and the intention is to perform a re-installation,
disable auto-boot from the ILOM and perform a reset.

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
sunt4-2 console login: #.
Serial console stopped.

-> set /HOST/domain/control auto-boot=disable
Set 'auto-boot' to 'disable' [disabled]

-> show /HOST/domain/control

 /HOST/domain/control
    Targets:

    Properties:
        auto-boot = disabled
        boot_guests = enabled

    Commands:
        cd
        reset
        set
        show

-> reset /HOST/domain/control
Are you sure you want to reset /HOST/domain/control (y/n)? y
Performing reset on /HOST/domain/control

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.

svc.startd: The system is down.
syncing file systems... done
NOTICE: Entering OpenBoot.
NOTICE: Fetching Guest MD from HV.
NOTICE: Starting additional cpus.
NOTICE: Initializing LDC services.
NOTICE: Probing PCI devices.
NOTICE: Finished PCI probing.

SPARC T4-2, No Keyboard
Copyright (c) 1998, 2018, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.38.16, 511.5000 GB memory available, Serial #99740538.
Ethernet address 0:21:28:f1:eb:7a, Host ID: 85f1eb7a.

{0} ok

Conclusions:

The SPARC Chassis, with various access methodologies, can achieve access to the OpenBoot / OpenFirmware prompt, for loading new operating systems, regardless of what was previously loaded on the chassis.

Monday, May 24, 2021

Oracle SPARC T4-4 - USB Boot & Install

[SPARC T4-4 Chassis Image, Courtesy Oracle]

Oracle SPARC T4-4 - USB Boot & Install

Abstract

UNIX Systems Manufacturers originated their markets as workstations, during a time when they used 32 bit systems and the rest of the PC market was concentrating on 8 and 16 bit systems, and some CPU vendors like Intel use segmentation to keep their 16 bit software alive while struggling to move to 32 bit architectures. Some of the original servers were stacked workstations on a rack in a cabinet. The former high-powered video cards were merely ignored, as remote management needed command line interfaces. Engineering quickly determined that console access needed to be built into a new class of systems: rack mounted servers. These early servers offered boot functionality from Network and Disk. One such boot capability was from USB Disk.This capability was later carried onto other chassis that Oracle would manufacture, such as the SPARC T4-4.

Creating a USB Boot Stick from Solaris

The USB port can be used to create a Solaris 11.4 USB Boot Stick from Solaris, after inserting a SanDisk USB stick into the front port next to the DVD Drive:

T5120/root# echo | format -e | grep -i SanDisk
       4. c7t0d0 <SanDisk'-Cruzer Fit-1.00 cyl 1945 alt 0 hd 255 sec 63>
       5. c8t0d0 <SanDisk'-Cruzer Fit-1.00 cyl 1945 alt 0 hd 255 sec 63>

T5120/root# ls -al *usb
-rw-r--r--   1 dh127087 staff    1217341440 May  3 19:38 sol-11_4-text-sparc.usb

T5120/root# time dd bs=16k if=sol-11_4-text-sparc.usb of=/dev/rdsk/c7t0d0s2
74300+1 records in
74300+1 records out

real    8m57.25s
user    0m0.47s
sys     0m13.99s

T5120/root# echo "par\nprint\n" | format -e c7t0d0 | tail -14 | nawk '$NF!="0" && !/partition/'
Total disk cylinders available: 148 + 0 (reserved cylinders)

Part      Tag    Flag     Cylinders       Size            Blocks
  0 unassigned    wm       0 - 147        1.13GB    (148/0/0) 2377620
  2 unassigned    wm       0 - 147        1.13GB    (148/0/0) 2377620

T5120/root#

This USB stick can now be tested from, from OpenBoot Firmware

Oracle SPARC T4-4

The Oracle SPARC T4-4 is a server with a 4th generation OpenSPARC processor. The SPARC T4 processor was manufactured to the same process size as the SPARC T3 CPU processor, but the core was upgraded, so equivalent throughput could be reached with half as many cores, at the same processor speed. The T4-4 Chassis comes with a Lights Out Management (LOM) capability referred to as Integrated Lights Out Management (ILOM.) Most remote systems management work can be done from the LOM. The system, when looking at the front of the chassis: the T5120 has 2x USB ports next to the DVD drive on the right and 2x USB ports located in the back left corner.

Attaching to the ILOM

The ILOM can be attached to via TCP/IP, if previously configured, or over a serial port.

T5120/user$ ssh root@sun1234-ilom
Password:

Oracle(R) Integrated Lights Out Manager
Version 3.2.6.8 r128095
Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.
Hostname: ORACLESP-1207BDY075

->

Insert USB Boot

The USB boot flash stick should be inserted into a powered down chassis, to boot from firmware.

-> show /system power_state actual_power_consumption

  /System
    Properties:
        power_state = Off
        actual_power_consumption = 37 watts

Power Up Chassis

After the USB boot stick is inserted, the chassis should be powered up from the ILOM.

-> start /SYS
Are you sure you want to start /SYS (y/n)? y
Starting /SYS

After the chassis is powered on, once the power usage increases, attach to the console

-> show /system power_state actual_power_consumption

  /System
    Properties:
        power_state = On
        actual_power_consumption = 1384 watts


-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.

{0} ok

Note: If the chassis was recently started, the ability to access a prompt does not really occur until after the actual power consumption rises to an expected level.
Note: if the "ok" prompt does not appear, press [RETURN] or [ENTER] key

Select USB Port

When a SanDisk USB Flash Sticks are plugged into the USB ports located to the right of the DVD drive, they can be seen at the OpenFirmware prompt, and can be selected into a copy-paste buffer, for easy use.

{0} ok show-disks
a) /reboot-memory@0
b) /pci@700/pci@1/pci@0/pci@0/LSI,sas@0/disk
c) /pci@500/pci@1/pci@0/pci@1/pci@0/pci@3/SUNW,emlxs@0,1/fp@0,0/disk
d) /pci@500/pci@1/pci@0/pci@1/pci@0/pci@3/SUNW,emlxs@0/fp@0,0/disk
e) /pci@400/pci@2/pci@0/pci@1/pci@0/pci@3/SUNW,emlxs@0,1/fp@0,0/disk
f) /pci@400/pci@2/pci@0/pci@1/pci@0/pci@3/SUNW,emlxs@0/fp@0,0/disk
g) /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/hub@3/storage@2/disk
h) /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/storage@2/disk
i) /pci@400/pci@1/pci@0/pci@0/LSI,sas@0/disk
j) /iscsi-hba/disk
m) MORE SELECTIONS
q) NO SELECTION
Enter Selection, q to quit: h
/pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/storage@2/disk has been selected.
Type ^Y ( Control-Y ) to insert it in the command line.
e.g. ok nvalias mydev ^Y
         for creating devalias mydev for /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/storage@2/disk
{0} ok

Note: the USB stick in position "h" (this lettered position may change as new USB sticks are plugged or unplugged) has it's device name copied into a "copy-paste" buffer by selecting "h"

Boot Solaris 11.4 from USB

After shutting down the OS, while on the console port, attempt to boot from 11.4, which is too new:

{0} ok boot ^Y
{0} ok boot /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/storage@2/disk
Boot device: /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/storage@2/disk  File and args:
/

Install Solaris 11.4

As the USB boot occurs, the Solaris 11.4 installer begins.

SunOS Release 5.11 Version 11.4.0.15.0 64-bit
Copyright (c) 1983, 2018, Oracle and/or its affiliates. All rights reserved.
Remounting root read/write
Probing for device nodes ...
Preparing image for use
Done mounting image
USB keyboard
 1. Arabic                        15. Korean
 2. Belgian                       16. Latin-American
 3. Brazilian                     17. Norwegian
 4. Canadian-Bilingual            18. Portuguese
 5. Canadian-French               19. Russian
 6. Danish                        20. Spanish
 7. Dutch                         21. Swedish
 8. Dvorak                        22. Swiss-French
 9. Finnish                       23. Swiss-German
10. French                        24. Traditional-Chinese
11. German                        25. TurkishQ
12. Italian                       26. UK-English
13. Japanese-type6                27. US-English
14. Japanese
To select the keyboard layout, enter a number [default 27]: 27

 1. Chinese - Simplified
 2. Chinese - Traditional
 3. English
 4. French
 5. German
 6. Italian
 7. Japanese
 8. Korean
 9. Portuguese - Brazil
10. Spanish
To select the language you wish to use, enter a number [default is 3]: 3

User selected: English
Configuring devices.
Hostname: solaris
 
 
Welcome to the Oracle Solaris installation menu

        1  Install Oracle Solaris
        2  Install Additional Drivers
        3  Shell
        4  Terminal type (currently xterm)
        5  Reboot

Please enter a number [1]: 1

                          Welcome to Oracle Solaris

   Thanks for choosing to install Oracle Solaris! This installer enables you
   to install the Oracle Solaris Operating System (OS) on SPARC or x86
   systems.

   The installation log will be at /system/volatile/install_log.

   How to navigate through this installer:
   - Use the function keys listed at the bottom of each screen to move from
     screen to screen and to perform other operations.
   - Use the up/down arrow keys to change the selection or to move between
     input fields.
   - If your keyboard does not have function keys, or they do not respond,
     press ESC; the legend at the bottom of the screen will change to show
     the ESC keys for navigation and other functions.

  F2_Continue  F6_Help  F9_Quit


                              Discovery Selection

   Select discovery method for disks

    Local Disks            Discover local disks

    iSCSI                  Discover iSCSI LUNs

 
F2_Continue  F3_Back  F6_Help  F9_Quit


                                     Disks

    Where should Oracle Solaris be installed?
    Minimum size: 4.1GB    Recommended minimum: 6.1GB

    Type     Size(GB) Boot  Device
    ----------------------------------------------------------------------
    scsi        279.4   +   SYS/MB/HDD4                  HITACHI
    scsi        279.4       SYS/MB/HDD0                  HITACHI
    usb           1.1       c2t0d0                       SanDisk'       <


    The following slices were found on the disk.

      Slice        #  Size(GB)             Slice        #  Size(GB)
      ------------------------             ------------------------
      rpool        0     279.4             Unused       5       0.0
      Unused       1       0.0             Unused       6       0.0
      Unused       3       0.0             Unused       7       0.0
      Unused       4       0.0             backup       2     279.4


 
F2_Continue  F3_Back  F6_Help  F9_Quit


                         Solaris Slices: 279.4GB scsi

   Oracle Solaris can be installed on the whole disk or a slice on the disk.

   The following slices were found on the disk.

     Slice        #  Size(GB)             Slice        #  Size(GB)
     ------------------------             ------------------------
     rpool        0     279.4             Unused       5       0.0
     Unused       1       0.0             Unused       6       0.0
     Unused       3       0.0             Unused       7       0.0
     Unused       4       0.0             backup       2     279.4

                              Use the whole disk
                            Use a slice on the disk

  F2_Continue  F3_Back  F6_Help  F9_Quit


                                System Identity

   Enter a name for this computer that identifies it on the network.
   It can contain letters, numbers, periods (.) and minus signs (-).  The
   name must start and end with an alphanumeric character and must contain
   at least one non-digit character.

   Computer Name: solaris

  F2_Continue  F3_Back  F6_Help  F9_Quit


                             Network Configuration

   Select a wired network connection to configure

     ^ net6 (e1000g4)
     | net7 (e1000g5)
     | net8 (e1000g6)
     | net9 (e1000g7)
     | net10 (e1000g8)
     | net11 (e1000g9)
     | net12 (e1000g10)
     | net13 (e1000g11)
     | net14 (e1000g0)
     | net15 (e1000g1)
     | net16 (nxge0)
     | net17 (nxge1)
     | net18 (nxge2)
     | net19 (nxge3)
     v net20 (nxge4)

  F2_Continue  F3_Back  F6_Help  F9_Quit


   Select how the network interface should be configured.

     DHCP              Allow DHCP to configure the interface

     Static            Configure the interface with a static IP address

  F2_Continue  F3_Back  F6_Help  F9_Quit


                              Time Zone: Regions

    Select the region that contains your time zone.

      Regions
      ----------------------------------------
      UTC/GMT
      Africa
      Americas
      Antarctica
      Asia
      Atlantic Ocean
      Australia
      Europe
      Indian Ocean
      Pacific Ocean

  F2_Continue  F3_Back  F6_Help  F9_Quit


                               Locale: Language

   Select the default language support and locale specific data format.
   These selections determine the language support, the default date and
   time, and other data formats.
   The language chosen automatically determines the available territories.

     Language
    ----------------------------------------
     No Default Language Support
     Chinese
     English
     French
     German
     Italian
     Japanese
     Korean
     Portuguese
     Spanish

  F2_Continue  F3_Back  F6_Help  F9_Quit


                               Locale: Territory

   Select the language territory

     Territory
    ----------------------------------------
     United States (en_US.ISO8859-1)
     United States (en_US.ISO8859-15)
     United States (en_US.ISO8859-15@euro)
     United States (en_US.UTF-8)

  F2_Continue  F3_Back  F6_Help  F9_Quit


                                 Date and Time

   Edit the date and time as necessary.
   Time shown is the system clock time in UTC and will be interpreted as
   such on installation.
   The time is in 24 hour format.

     Year:    2021 (YYYY)
     Month:     05 (1-12)
     Day:       22 (1-31)
     Hour:      05 (0-23)
     Minute:    46 (0-59)

  F2_Continue  F3_Back  F6_Help  F9_Quit


                                   Keyboard

   Select your keyboard.

   ^ German
   | Italian
   | Japanese-type6
   | Japanese
   | Korean
   | Latin-American
   | Norwegian
   | Portuguese
   | Russian
   | Spanish
   | Swedish
   | Swiss-French
   | Swiss-German
   | Traditional-Chinese
   | TurkishQ
   | UK-English
   - US-English

  F2_Continue  F3_Back  F6_Help  F9_Quit
 
 
                                     Users

    Define a root password for the system and user account for yourself.


    System Root Password (required)

     Root password:    solar1s
     Confirm password: solar1s

    Create a user account (optional)

     Your real name:
     Username:
     User password:
     Confirm password:

  F2_Continue  F3_Back  F6_Help  F9_Quit

 
                            Support - Registration

     Provide your My Oracle Support credentials to be informed of
     security issues, enable Oracle Auto Service Requests.

     See http://www.oracle.com/goto/solarisautoreg for details.

       Email: anonymous@oracle.com
              Easier for you if you use your My Oracle Support email
              address/username.

       Please enter your password if you wish to receive security
       updates via My Oracle Support.

              My Oracle Support password:

  F2_Continue  F3_Back  F6_Help  F9_Quit

 
                             Installation Summary

   Review the settings below before installing. Go back (F3) to make changes.

   - Software: Oracle Solaris 11.4 SPARC
   |
   | Root Pool Disk: 279.4GB scsi
   |
   | Computer name: solaris
   |
   | Network:
   | DHCP Configuration: net6/v4
   |
   | Time Zone: UTC
   | Locale:
   | Default Language: English
   | Language Support: English (United States)
   | Keyboard: US-English
   | No user account
   |
   v Support configuration:

  F2_Install  F3_Back  F6_Help  F9_Quit

 
                           Installing Oracle Solaris

               Preparing for Installation

              [                       (4%)                       ]

  F9_Quit

 
                             Installation Complete


   The installation of Oracle Solaris has completed successfully.

   Reboot to start the newly installed software or Quit if you wish to
   perform additional tasks before rebooting.

   The installation log is available at /system/volatile/install_log. After
   reboot it can be found at /var/log/install/install_log.


  F4_View Log  F7_Halt  F8_Reboot  F9_Quit
 

 May 22 06:22:23 solaris reboot: initiated by root
 

Welcome to the Oracle Solaris installation menu

        1  Install Oracle Solaris
        2  Install Additional Drivers
        3  Shell
        4  Terminal type (currently xterm)
        5  Reboot

Please enter a number [1]: syncing file systems... done
rebooting...
Resetting...
NOTICE: Entering OpenBoot.
NOTICE: Fetching Guest MD from HV.
NOTICE: Starting additional cpus.
NOTICE: Initializing LDC services.
NOTICE: Probing PCI devices.
NOTICE: Finished PCI probing.

SPARC T4-4, No Keyboard
Copyright (c) 1998, 2018, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.38.16, 1023.5000 GB memory available, Serial #99743488.
Ethernet address 0:21:28:f1:f7:0, Host ID: 85f1f700.
 
Boot device: /pci@400/pci@1/pci@0/pci@0/LSI,sas@0/disk@w5000cca0252bf86d,0:a  File and args:
/
SunOS Release 5.11 Version 11.4.0.15.0 64-bit
Copyright (c) 1983, 2018, Oracle and/or its affiliates. All rights reserved.
Loading smf(7) service descriptions: 238/238
Booting to milestone "svc:/milestone/config:default".
Configuring devices.
Loading smf(7) service descriptions: 2/2
Booting to milestone "all".
Hostname: solaris
May 22 06:35:06 solaris sendmail[1502]: My unqualified host name (solaris) unknown; sleeping for retry
May 22 06:35:06 solaris sendmail[1507]: My unqualified host name (solaris) unknown; sleeping for retry

solaris console login:

UnConfigure / Configure

Solaris 10, offered an option to perform a "sys-unconfig", to restore an OS back to factory settings. In Solaris 11, this has been replaced with another option called "sysconfig configure -s" or "sysconfig configure -s --destructive" to destroy the initial user home account to also be destroyed.

This option is good if moving a chassis to a different location.