---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Oracle Solaris LDOM

# Oracle
Solaris LDOM discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Oracle Solaris LDOM discovery

Oracle Solaris LDOM discovery in ServiceNow Australia release (and later) enables automated identification and mapping of Solaris Logical Domains (LDOMs) as part of horizontal discovery.
This leverages the Solaris LDOM infrastructure pattern and Solaris LDOM shared library pattern to collect detailed information about LDOM controllers and guest virtual machines on Solaris servers.
Show full answer Show less  
The Solaris LDOM infrastructure pattern triggers automatically during Solaris Server discovery to detect LDOM controllers, while the Solaris LDOM shared library pattern runs as an extension to align serial number data between LDOM machines and their controllers.

## Prerequisites

To successfully run the Solaris LDOM discovery patterns, ensure that the users executing discovery have required permissions for specific Solaris commands including `virtinfo -a`, `ldm -V`, `ldm list-rsrc-group -a`, `sneep`, `prtdiag`, and others. These commands are essential for gathering LDOM version, role, state, serial numbers, and establishing relationships between LDOM controllers and guests.

Note that some commands are conditional and may not run on every discovery. For example, the `sneep` command is preferred for retrieving serial numbers but `prtdiag` is used as a fallback if `sneep` is unavailable.

## Data Collected

The discovery adds data to the `cmdbcisolarisserver` table with key fields including:

* **ldomversion:** Version of LDOM installed on the controller
* **ldomrole:** The role of the system ("controller" or "guest")
* **ldomstate:** Current state of the LDOM implementation
* **serialnumber:** Serial number of the machine
* **virtual:** Indicates if the machine is a virtual guest
* **ram:** Available memory on the LDOM controller
* **cpucorecount:** Number of CPU cores on the LDOM controller

## Relationships

The discovery establishes configuration item (CI) relationships representing the hosting structure:

* **LDOM controller** hosts one or more **LDOM guest VMs** (relationship type: Hosted on::Hosts)

## Benefits for ServiceNow Customers

This discovery capability provides ServiceNow customers with accurate, automated visibility into Solaris LDOM environments, enabling better infrastructure management and service mapping. By capturing detailed LDOM attributes and relationships, customers can improve asset tracking, impact analysis, and operational insights within their CMDB.  
Discovery uses the Solaris Logical Domain (LDOM)
infrastructure pattern and Solaris LDOM shared library pattern to find all LDOM
data. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Discovery uses these patterns to run horizontal discovery. You can use the
patterns on the ServiceNow AI Platform using the Australia release or
later.

The Solaris LDOM infrastructure pattern is triggered automatically on
Solaris Server discovery. The pattern verifies if there is an LDOM controller, and stops
running if it doesn't find a controller.

The Solaris LDOM shared library pattern is run as an Extension Section to
the Solaris Server pattern​. The pattern modifies the Serial Number (SN) on
LDOM machines so that it matches the SN populated by the Solaris LDOM
infrastructure pattern. For further information about Solaris Server, see [Solaris discovery](https://www.servicenow.com/docs/AYZ72Iwe_0sR33CqAZL_Ng "Discovery identifies and classifies information about Solaris computers.").

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).

## Prerequisites {#solaris-ldom-discovery__section_ybt_bn4_xkb}

LDOM commands when running the Solaris LDOM infrastructure pattern
:   Ensure the relevant users have permissions to execute the following used commands for
    the Solaris LDOM infrastructure pattern:

    * "sudo /usr/sbin/virtinfo -a"
    * "sudo /usr/sbin/ldm -V"
    * "hostname"
    * "svcs ldmd"
    * "sudo /usr/sbin/ldm list-rsrc-group -a"
    * "sudo /usr/sbin/sneep -T \| grep ChassisSerialNumber 2\> /dev/null"
    * "/usr/sbin/prtdiag -v \| awk '/Chassis Serial/{getline; getline; print}'"
    * "sudo /usr/sbin/ldm list"  
      Note:  
      Some of these commands are used with conditions, and will not be executed on each discovery. For example, the main way to get the SN for servers is by using the 'sneep' command. However, this is not available by default on Solaris servers, so 'prtdiag' is used as an alternative method to get the SN.
    {#solaris-ldom-discovery__ul_sdc_zhf_wnb}

Important LDOM commands when running the Solaris LDOM shared library
pattern
:   Ensure the relevant users have permissions to execute the following used commands for
    the Solaris LDOM shared library pattern:

    * "sudo /usr/sbin/virtinfo -a"
    * "sudo /usr/sbin/sneep -T \| grep ChassisSerialNumber 2\> /dev/null"
    * "hostname"
    {#solaris-ldom-discovery__ul_lqg_q1g_wnb}
:   Ensure the relevant users have the permissions to execute the LDOM
    virtinfo command. This command ensures the proper LDOM role can be
    established.
:   Ensure the relevant users have the permissions to execute the LDOM "sudo /usr/sbin/ldm list" command for listing Guest VMs on the LDOM controller.
    This is required in order to set relations between the LDOM controller and the LDOM
    Guest VMs.
:   One of the 'sneep' or 'prtdiag' Serial Number
    commands has to return a correct response in order to correctly set the SN.

## Data collected by Discovery during horizontal discovery {#solaris-ldom-discovery__section_tbt_kbg_wnb}

The data discovered by both patterns includes the following tables and fields.
{#solaris-ldom-discovery__table_hy1_rbg_wnb__entry__2}

| Table and field | Description |
|-|-|
| Solaris Server \[cmdb_ci_solaris_server\] ||
| ldom_version | The LDOM version installed on the LDOM controller. |
| ldom_role | The LDOM role; "controller" or "guest".​ |
| ldom_state | The state of the LDOM implementation on the LDOM controller. |
| serial_number | The serial number of the machines. |
| virtual | Whether or not a virtual machine (for Guest VMs) is used for the LDOM controller.​ |
| ram | The memory available on the LDOM controller.​ |
| cpu_core_count | The number of CPU cores on the LDOM controller. |
[ ]

{#solaris-ldom-discovery__table_hy1_rbg_wnb}

## CI relationships {#solaris-ldom-discovery__section_whr_ycg_wnb}

{#solaris-ldom-discovery__table_hhl_r2g_wnb__entry__3}

| CI | Relationship | CI |
|-|-|-|
| LDOM controller | Hosted on::Hosts | LDOM Guest VM |
[ ]

{#solaris-ldom-discovery__table_hhl_r2g_wnb}