Page tree
Skip to end of metadata
Go to start of metadata

The Host Side Linking pattern for Solaris is designed to scan a host in order to establish relationships between:

  • Servers (both physical and virtual (Solaris Zones), LDOM guests hosts are supported) and any external (storage volumes on the remote SAN system) or local storage sources (hard drives);
  • Local file systems hosted on a host and the device that provides file systems with storage capacity;

The pattern also creates disk drive nodes for the local disk drives.

The illustration below shows a discovered Solaris host (physical) with the external storage volumes and internal virtual disk drives:

How it Work

The Host Side Linking pattern for Solaris triggers upon host creation or confirmation, where the OS type attribute matches regex 'Solaris'. First, the pattern identifies the different internal drives and/or connected storage volumes, and then creates the corresponding disk drive nodes in the BMC Discovery environment.

The Host Side Linking Pattern for Solaris creates the following relationships:

  • From host to storage device (disk drive or storage volume);
  • From the local file system to the appropriate storage device (disk drive or storage volume);

The pattern may stop its execution if:

  • the pattern was not able to locate a command’s full path (by using “which” system script);
  • no local file systems were found on the host.


As no storage information is available from inside the virtual Zone host (with the exception of the ZFS zpool), the pattern retrieves all the information from the global zone node (physical) and uses special Zone Storage Resource Detail, attached to the Zone Container Software Instance, to provide valuable information to the zone host, as illustrated below:


The current version of the Host Side Linking pattern for Solaris pattern requires the following scanning order to be strictly followed to ensure collection of all available information in a single pass:

  1. Scanning the storage system providing storage to the hosts;
  1. Scanning of the physical host hosting zones;
  1. Scanning of the zone host(s).

The Host Side Linking Pattern for Solaris launches commands that may require specific execution privileges. The pattern first run commands as the normal user that discovery is using. In case of failure, commands are rerun using PRIV_RUNCMD. In that case, PRIV_RUNCMD will need to be configured to use an appropriate privilege elevation mechanism (see Adding privileged execution to commands for detailed information). The only exception consists in the “format” command which always requires privileged execution.

The list of commands that the Solaris Storage pattern may run includes:

  • format – mandatory command. The output of this command provides HostSide Linking with critical and valuation information. (Always requires privileged execution. Discovery runs this command in order to read existing configuration).
  • prtpicl – to find all the storage volumes (LUNs) connected to the host.
  • metastat – to collect metadevice information (if any).
  • zpool – to collect zpool information, if any. This is the only command that runs on the virtual host (Solaris Zone).
  • iostat – to obtain local drive information such as size, model, vendor etc.
  • raidctl – to obtain hardware RAID information, if any.
  • metaset – to collect information about the devices used in the SVM metasets.
  • scdidadm – to get mapping between DID device name and the actual devices it represents.
  • zonecfg - runs on the physical Solaris host (“global” zone) to collect Solaris zone(s) information (virtual hosts will use this information for HSL).

  • /opt/SUNWldm/bin/ldm list-domain -l -p (Always requires privileged execution.)

Note: Depending on the host’s configuration, some commands may remain unused.

  • No labels