The Host Side Linking pattern for Solaris is designed to scan a host in order to establish relationships between:
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:
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:
The pattern may stop its execution if:
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:
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:
Note: Depending on the host’s configuration, some commands may remain unused.