Solaris discovery

Discovery identifies and classifies information about Solaris computers.

Note: See the knowledge article KB0687582 for information on model_id and manufacturer.

Supported operating systems

• Oracle Solaris 10
• Oracle Solaris 11

Prerequisites

• Handle truncated command line parameters

  Discovery stores data in the [cmdb_running_process] table with command line parameters truncated to 80 characters. This can cause multiple applications to be merged into one CI. To get the full command line and prevent this issue, run pargs -a and parse the result.

• Install SNEEP

  To use patterns to find Solaris computers, install SNEEP. Without it, Discovery cannot find the serial number.

• Configure unique serial numbers for Solaris zones

  Configure each zone to return a unique serial number. If zones return the same number, CI identification fails.

  Note: Solaris discovery only supports local zones installed on the same host as the global zone. If the local zone is installed on a different host from the global zone, the zoneadm list -cip command can't retrieve the UUID for the local zone.

• Install the LSOF command

  The Solaris - ADM probe requires the LSOF command to be installed.

• Configure SSH credentials

  Configure SSH credentials for the systems you are discovering.

  For a list of privileged commands that you need for Discovery and Service Mapping, see Service Mapping commands requiring a privileged user. This list includes commands that require elevated rights to discover and map Unix-based hosts in your organization.

• Set the preferred IP address version for network adapter discovery

  Starting with Visibility Content version 6.32.0, if your network adapters support both IPv4 and IPv6, the IPv4 address is populated by default in the IP address [ip_address] field on the Network Adapter [cmdb_ci_network_adapter] table. To control which IP version is populated, see Set the preferred IP version for network adapter discovery.

Classifier, probes, and pattern

*For new instances, these probes are inactive on the classifier. Discovery uses patterns for discovery.

^This probe remains active by default, even when Discovery uses pattern discovery.

To use patterns, verify that the correct pattern is specified in the horizontal pattern probe on the classifier. See Add the Horizontal Pattern probe to a classifier for instructions.

Data collected

* To discover Fujitsu PRIMEPOWER devices, you must install Oracle SNEEP and run Solaris discovery with root credentials.

** Starting with Visibility Content version 6.32.0, for network adapters that support both IPv4 and IPv6, the IPv4 address is populated by default. Before this release, the populated value was selected randomly. To control which IP version is populated, see Set the preferred IP version for network adapter discovery.

Solaris zone discovery

Discovery maps the relationships between global and local Solaris zones upon detection.

In the following example, a Solaris global zone contains two local zones: zone01 and zone02. Each local zone is represented by a physical Solaris CI record and a Virtual Machine Instance record. Each of the local zones is tied to a Zone Server, demonstrating how virtualization relates to the global zone (mmp1).

The TCP connection and process information for local zone servers must be collected by running commands on their parent global zone. The relationship path between the local and global zone physical machines must be established before TCP connection and process information for local zone servers can be collected.

Case 1: Global zone is discovered first.

• The system creates the Solaris server CI for the global zone.
• Discovery detects the local zones, creates a hypervisor zone server record, and creates a virtual machine instance record for each Solaris device in the local zone.
• Discovery creates the relationship between the hypervisor record and the VM instance record.

Case 2: Local zone is discovered first.

• The system creates the Solaris server CI for the local zone.
• Discovery sets the correlation ID, so that it can be reconciled during later global zone discoveries.

Case 3: Global zone is discovered after local zone Solaris server CIs are created.

• Global zone Discovery detects local zones.
• Discovery creates a hypervisor zone server record, and creates a virtual machine instance record for each Solaris device in the local zone.
• Discovery creates the relationship between the hypervisor record and the VM instance record. In addition, it creates the relationship between the physical local zone VM and its virtual machine instance record.
• The global zone runs the Solaris - ADM probe on itself, filtering by the local zone, and updates the physical local zone VMs with this data.

Case 4: The relationship path between physical local and global zone machines is established.

Subsequent discoveries of the global zone refresh the TCP connection and process information for the contained local zones.

When the system discovers a global zone, the Solaris - Zones & ADM Launcher probe triggers the Solaris - ADM probe to explore the global zone and each local zone found. Because the Solaris - ADM probe must run on the global zone to detect TCP connection and process information from its local zones, you might see multiple ECC queue records that appear identical.

Examining the payload shows that each probe targets a different zone CI to filter on and update.

Note: cmdb_ci_solaris_instance extends cmdb_ci_vm_instance.

Parent Topic:Operating systems discovery