Oracle Integrated Lights Out Manager (iLOM) is a powerful tool for managing SPARC T4 servers remotely. It allows system administrators to monitor hardware status, retrieve configuration details, and perform management tasks without physical access to the server. Whether you're troubleshooting, performing routine maintenance, or setting up a new system, knowing how to access and navigate iLOM is essential. In this article, we'll explore the various methods to connect to the iLOM on a SPARC T4 server—via the serial port, NET MGMT port, or web browser—and demonstrate how to retrieve key configuration details like network information for the iLOM (using /SP), and system information (using /System, /Sys and /Host).

This guide is aimed at IT System Administrators familiar with server management but may need a refresher for working with iLOM on SPARC T4 hardware.

Methods to Connect to Oracle iLOM

The SPARC T4 server’s iLOM can be accessed in multiple ways, each suited to different scenarios. Below, we’ll cover the three primary methods: the serial port, the NET MGMT port, and a web browser.

1. Connecting via the Serial Port

The serial port provides a direct, low-level connection to iLOM, ideal for situations where network access isn’t available or when troubleshooting hardware issues. You’ll need a serial cable (typically an RJ45-to-DB9 adapter, or RJ45-to-USB adapter) and a terminal emulator like PuTTY (Windows) or minicom (Linux).

Setting Up PuTTY on a Windows Client

Install PuTTY: Download and install PuTTY from putty.org.
Connect the Serial Cable: Plug one end into the SPARC T4’s SER MGT port and the other into your Windows client’s serial port (or a USB-to-serial adapter if needed).
Configure PuTTY:
- Open PuTTY and select Serial as the connection type. Refer to the image below.

Set the Serial line to the appropriate COM port (e.g, COM1 - check Device Manager to confirm).
Use these settings:
- Speed (baud rate): 9600
- Data bits: 8
- Stop bits: 1
- Parity: None
- Flow control: None
Click Open to start the session.

Log In: When the terminal opens, press Enter. You’ll see the iLOM login prompt. Use your iLOM credentials (default is root/changeme unless changed). You are now logged into the server’s service processor (abbreviated to SP).

Setting Up a Serial Connection on a Linux Client

Install minicom: On a Debian-based system, run sudo apt-get install minicom. For Red Hat-based systems, use sudo yum install minicom.
Connect the Serial Cable: Attach it to the SER MGT port and your Linux client’s serial port (e.g., /dev/ttyS0 or /dev/ttyUSB0 for USB adapters).
Launch minicom:
- Run sudo minicom -s to enter setup mode.
- Select Serial port setup.
- Set the serial device (e.g., /dev/ttyS0), baud rate (9600), 8N1 (8 data bits, no parity, 1 stop bit), and disable hardware/software flow control.
- Save the configuration and exit setup.
- Connect by selecting Exit from the main menu.
Log In: Press Enter at the prompt and log in with your iLOM credentials.

2. Connecting via the NET MGMT Port

The NET MGMT port allows network-based access to iLOM via SSH or Telnet, assuming it’s connected to your network and configured with an IP address.

Check Network Configuration: If the IP isn’t set, use the serial method first to configure it (see examples below).
SSH from a Client:
- On Windows, use PuTTY: Select SSH, enter the iLOM IP address, and connect on port 22.
- On Linux, run ssh root@<iLOM_IP> from a terminal.
Log In: Enter your iLOM credentials at the prompt.

3. Connecting via a Web Browser

The iLOM web interface is user-friendly and perfect for quick checks or when a GUI is preferred.

Ensure Network Access: The NET MGMT port must be connected and configured with an IP address.
Open a Browser: Use a modern browser (e.g., Chrome, Firefox) and navigate to https://<iLOM_IP>.
Log In: Enter your credentials in the web interface. Ignore any SSL warnings if using a self-signed certificate (common in default setups).
Navigate: Use the dashboard to view system info or access the remote console.

Retrieving status information from iLOM

Once connected - whether via serial, SSH, or the web interface - you can retrieve a wealth of information using iLOM commands. Below are a few basic examples of common tasks, assuming you’re at the -> prompt (the iLOM CLI).

When you first login, the screen will look like this:


Hostname: my_server_name

->

Enter the show command to see available options.


-> show

 /
    Targets:
        HOST
        STORAGE
        SYS
        System
        SP

    Properties:

    Commands:
        cd
        show

The items listed under Target are available for further exploration. In the following sections, we drill down into these targets, to show the basic functionality of the iLOM.

Whenever you see the word Target in the output, you can select the listed item for drilldown. For example, we can see from the above output, there is an item called STORAGE. So let’s drill down.

-> show STORAGE

 /STORAGE                                    ------> drill down
    Targets:
        raid 
...


-> show STORAGE/raid                        ------> drill down

 /STORAGE/raid
    Targets:
        controller@04:00.0_508002000193ded0
        controller@0b:00.0_508002000193ded1
        controller@0f:00.0_500605b007bef8a0
        controller@10:00.0_500605b007beba90

 show /STORAGE/raid/controller@04:00.0_508002000193ded0    ------> drill down

    Targets:
        disk_id0

    Properties:
        fru_manufacturer = LSI Logic
        fru_model = SG-SAS6-INT-Z
        fru_serial_number = 508002000193ded0
        fru_name = RF On-Board
        pci_vendor_id = 0x00001000
        pci_device_id = 0x00000072
        pci_subvendor_id = 0x00001000
        pci_subdevice_id = 0x00000072
        firmware_version = 09.05.00.00
        raid_levels = 0, 1, 1E
        max_disks = 128
        max_raids = 2
        max_global_hot_spares = 2
        min_stripe_size = 64
        max_stripe_size = 64

...
... etc.

Checking Network Information

Using /SP

To view the Service Processor’s (SP or iLOM) network settings:

-> show /SP/network

Output might look like:

/SP/network
    /SP/network
    Targets:
        interconnect
        ipv6
        test

    Properties:
        commitpending = (Cannot show property)
        dhcp_clientid = none
        dhcp_server_ip = none
        ipaddress = 10.20.30.40
        ipdiscovery = static
        ipgateway = 10.20.30.1
        ipnetmask = 255.255.255.0
        macaddress = 00:10:E0:45:F5:55
        managementport = MGMT
        outofbandmacaddress = 00:10:E0:45:F5:55
        pendingipaddress = 10.20.30.40
        pendingipdiscovery = static
        pendingipgateway = 10.20.30.1
        pendingipnetmask = 255.255.255.0
        pendingmanagementport = MGMT
        pendingvlan_id = (none)
        sidebandmacaddress = 00:16:E1:85:P5:84
        state = enabled
        vlan_id = (none)

This shows the IP address, gateway, subnet mask, and MAC address of the iLOM interface. Note: This interface is also referred to as the Service Processor, and is denoted by the letters SP in /SP .

Checking System Status

Using /System

To get an overview of the server’s status, including some environment parameters, and network configurations..

-> show /System

Example output:

 /System
    Targets:
        Open_Problems (0)
        Processors
        Memory
        Power
        Cooling
        Storage
        Networking
        PCI_Devices
        Firmware
        Log

    Properties:
        health = OK
        health_details = -
        open_problems = 0
        type = Rack Mount
        model = SPARC T4-1
        qpart_id = urn:uuid:2bf48bcd-07d5-11e0-9a9f-080020a9ed93
        part_number = 32547482+1+1
        serial_number = AK00194900
        system_identifier = (none)
        system_fw_version = Sun System Firmware 8.9.11 2018/11/28 07:59
        primary_operating_system = Oracle Solaris 11.2 SPARC
        primary_operating_system_detail = -
        host_primary_mac_address = Not Supported
        ilom_address = 10.20.30.40
        ilom_mac_address = 01:13:E0:47:F5:33
        locator_indicator = Off
        power_state = On
        actual_power_consumption = 341 watts
        action = (none)

This confirms the system is powered on and healthy, and provides the unit’s serial number (required when raising a service request). The Open Problems target is key here, as it will show problems that require your attention.

You can drill down and check, for example, the network card’s status.

-> show System/Networking/

 /System/Networking
    Targets:
        Ethernet_NICs
        Infiniband_HCAs

    Properties:
        health = OK
        health_details = -
        installed_eth_nics = 4
        installed_infiniband_hcas = 1

Using /SYS

/SYS gives you access to more server side hardware. For example, power supply units (PS0 and PS1), the motherboard (MB), local hard drives (HDD3 and HDD4)

-> show SYS

 /SYS
    Targets:
        CONNBD
        DVD
        FANBD
        FAN_FAULT
        HDD0
        HDD4
        INTSW
        MB
        MB_ENV
        OK
        PDB
        PS0
        PS1
        PS_FAULT
        PWRBS
        SASBP
        SERVICE
        TEMP_FAULT
        T_AMB
        USBBD
        VPS
        VPS_CPUS
        VPS_MEMORY

    Properties:
        type = Host System
        ipmi_name = /SYS
        keyswitch_state = Normal
        product_name = SPARC T4-1
        product_part_number = 32547482+1+1
        product_serial_number = AK00194900
        product_manufacturer = Oracle Corporation
        fault_state = OK
        clear_fault_action = (none)
        power_state = On

Checking Host Status

To check the SPARC T4’s operating system’s state:

-> show /HOST

Example output:

/HOST
    Targets:
        bootmode
        console
        diag
        domain
        tpm

    Properties:
        autorestart = reset
        autorunonerror = false
        bootfailrecovery = poweroff
        bootrestart = none
        boottimeout = 0
        hw_bti_mitigation = default (enabled)
        hypervisor_version = Hypervisor 1.15.16 2018/11/28 07:41
        macaddress = 00:22:e0:65:g5:4d
        maxbootfail = 3
        obp_version = OpenBoot 4.38.16 2018/11/28 07:24
        post_version = POST 4.38.16 2018/11/28 07:29
        send_break_action = (Cannot show property)
        status = Solaris running
        sysfw_version = Sun System Firmware 8.9.11 2018/11/28 07:59

We can see the server’s boot configuration, and that Solaris OS is running.

Additional Useful Commands

Locator -> set /System locator_indicator=on | off (switches the server’s locator light on or off)
Faults: -> show faulty (lists any hardware issues)
Firmware Version: -> version (shows firmware eg. 3.2.6.8 SP firmware build number: 128095 SP

Tips for server administrators

Default Credentials: If unchanged, use root/changeme. Change them immediately for security.
Serial as a Fallback: Always keep a serial cable handy, with both types of adapters, i.e. DB9 and USB - then network issues won’t stop you from accessing iLOM.
Web Interface: Great for quick checks, but the CLI (via serial or SSH) offers more granularity.
Documentation: Oracle’s official SPARC T4 iLOM docs are a goldmine - bookmark them!

Conclusion

Mastering iLOM on a SPARC T4 server is an essential skill for any SPARC server administrator. Whether you prefer a serial connection, SSH via the NET MGMT port, or a web interface, iLOM gives you the tools to manage your server.

If you’ve got any iLOM tricks to share, drop a comment below!

How to Check the status of an Oracle SPARC T4 Server using the service processor CLI

Table of contents