Oracle Solaris LDOM discovery

  • Release version: Xanadu
  • Updated August 1, 2024
  • 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 utilizes the Solaris Logical Domain (LDOM) infrastructure and shared library patterns to identify and collect detailed information about Solaris LDOM environments. This discovery capability is available from the Xanadu release onward and runs as part of horizontal discovery on Solaris servers. It automatically detects LDOM controllers and gathers relevant data from both controllers and guest virtual machines (VMs).

    Show full answer Show less

    Key Features

    • Solaris LDOM infrastructure pattern: Triggered automatically during Solaris Server discovery, it identifies the presence of LDOM controllers and gathers essential configuration details.
    • Solaris LDOM shared library pattern: Runs as an extension to the Solaris Server pattern, ensuring the serial numbers of LDOM guest machines align with the controller’s serial number for accurate identification.
    • Command requirements: Discovery requires execution permissions for specific Solaris LDOM commands such as virtinfo, ldm, sneep, and prtdiag. These commands help verify LDOM roles, states, and hardware details.
    • Fallback methods for serial number retrieval: Uses sneep primarily and falls back to prtdiag if sneep is unavailable, ensuring serial number accuracy.
    • Relationship mapping: Establishes relationships between LDOM controllers and guest VMs to reflect the hosting environment within the CMDB.

    Data Collected

    The discovery populates the cmdbcisolarisserver table with key fields including:

    • ldomversion: Version of LDOM installed on the controller.
    • ldomrole: Role of the machine, either "controller" or "guest".
    • ldomstate: Current state of the LDOM on the controller.
    • serialnumber: Serial number of the machine, critical for accurate identification.
    • virtual: Indicates if the machine is a virtual guest VM.
    • ram: Memory available on the LDOM controller.
    • cpucorecount: Number of CPU cores on the LDOM controller.

    Practical Considerations for ServiceNow Customers

    • Ensure user permissions are configured to allow execution of required Solaris LDOM commands for successful discovery.
    • Update the Discovery and Service Mapping Patterns application to the latest version from the ServiceNow Store to leverage improved LDOM discovery functionality.
    • Use this discovery capability to maintain an accurate and comprehensive CMDB reflection of Solaris LDOM environments, which supports better infrastructure visibility and management.
    • Leverage the established CI relationships to understand hosting and dependency mappings between LDOM controllers and guest VMs.

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