Oracle Solaris LDOM discovery

  • Release version: Yokohama
  • Updated January 30, 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 the Yokohama release (January 30, 2025) leverages Solaris Logical Domain (LDOM) infrastructure and shared library patterns to discover complete LDOM data on Solaris servers. This discovery is part of horizontal discovery on the ServiceNow AI Platform and requires the latest Discovery and Service Mapping Patterns application from the ServiceNow Store. The Solaris LDOM infrastructure pattern triggers automatically during Solaris Server discovery, detecting LDOM controllers and halting if none are found. The Solaris LDOM shared library pattern runs as an extension to synchronize serial numbers between LDOM machines and their controllers.

    Show full answer Show less

    Prerequisites

    To enable successful LDOM discovery, ensure relevant users have proper permissions to execute specific Solaris commands critical to the discovery patterns:

    • For Solaris LDOM infrastructure pattern: Commands such as 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, /usr/sbin/prtdiag -v, and sudo /usr/sbin/ldm list must be executable.
    • For Solaris LDOM shared library pattern: Commands including sudo /usr/sbin/virtinfo -a, sudo /usr/sbin/sneep -T | grep ChassisSerialNumber, hostname, and sudo /usr/sbin/ldm list must be executable.

    These commands facilitate role establishment, serial number retrieval, and mapping relationships between LDOM controllers and guest virtual machines. The discovery uses alternative commands for serial number retrieval when primary methods are unavailable.

    Data Collected

    The discovery populates key fields in the cmdbcisolarisserver table, including:

    • ldomversion: Version of LDOM on the controller.
    • ldomrole: Role designation as "controller" or "guest".
    • ldomstate: Current state of the LDOM implementation.
    • serialnumber: Machine serial number synchronized between controller and guests.
    • virtual: Indicates if the machine is virtual (for guest VMs).
    • ram: Memory available on the LDOM controller.
    • cpucorecount: Number of CPU cores on the LDOM controller.

    Relationships

    Discovery establishes relationships between LDOM controllers and guest VMs, specifically the "Hosted on::Hosts" relationship linking guest VMs to their controller.

    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 Yokohama 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