Oracle Solaris LDOM discovery

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    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 uses the Solaris Logical Domain (LDOM) infrastructure and shared library patterns to identify and collect data on Solaris LDOM environments. This discovery is part of horizontal discovery and requires the Discovery and Service Mapping Patterns application, preferably the latest version from the ServiceNow Store. The patterns operate on the ServiceNow AI Platform starting with the Zurich release or later.

    Show full answer Show less

    The Solaris LDOM infrastructure pattern automatically triggers during Solaris Server discovery to detect the presence of an LDOM controller and halts if none is found. The Solaris LDOM shared library pattern runs as an extension to the Solaris Server pattern, aligning serial number data between LDOM machines and the infrastructure pattern.

    Prerequisites

    To successfully run Solaris LDOM discovery, users must have permissions to execute specific Solaris commands used by each pattern. Key commands include:

    • For the Solaris LDOM infrastructure pattern: Commands such as sudo /usr/sbin/virtinfo -a, sudo /usr/sbin/ldm -V, hostname, svcs ldmd, and others related to listing resource groups and retrieving chassis serial numbers.
    • For the Solaris LDOM shared library pattern: Commands like sudo /usr/sbin/virtinfo -a, sudo /usr/sbin/sneep for chassis serial numbers, hostname, and sudo /usr/sbin/ldm list to list guest virtual machines.

    Note that serial number retrieval uses either the sneep or prtdiag commands, depending on availability. Proper command permissions ensure accurate role identification, serial number collection, and relationship mapping between LDOM controllers and guest VMs.

    Data Collected

    During discovery, data is gathered into the Solaris Server configuration item table (cmdbcisolarisserver) with key fields including:

    • ldomversion: The installed LDOM version on the controller.
    • ldomrole: The role of the system, either "controller" or "guest".
    • ldomstate: The current state of the LDOM implementation.
    • serialnumber: The machine’s serial number.
    • virtual: Whether the machine is a virtual machine (for guest VMs).
    • ram: Available memory on the LDOM controller.
    • cpucorecount: Number of CPU cores on the LDOM controller.

    Additionally, discovery establishes CI relationships indicating hosted-on relationships between LDOM controllers and their guest virtual machines.

    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 may 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 Zurich 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.

    Visit the ServiceNow Store website 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.

    Prerequisites

    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.​
    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”​
    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

    The data discovered by both patterns includes the following tables and fields.

    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.

    CI relationships

    CI Relationship CI
    LDOM controller Hosted on::Hosts LDOM Guest VM