Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend


The scripts you develop need to perform operations in the correct order to run successfully. Mapping out what the dependencies are helps you determine the sequence in which steps must take place. The following is a list of major cluster configuration tasks along with what their dependencies are.

  • Shared storage configuration—If VxVM software is chosen for your volume manager, mirrored volumes can be created before the cluster software is loaded, but since VxVM software is not cluster-aware, these volumes need to be registered with the cluster after the cluster software is installed and configured. Solstice DiskSuite is cluster-aware and should be used to configure your shared storage after the cluster is operational.

  • Data Agent package addition—Can be loaded after the Sun Cluster software core component packages are installed and while the cluster is active or inactive.

  • NAFO configuration—This is not tied to any particular data agent or service. Must be configured while the cluster node is active. For testing purposes, a NAFO group consisting of only a single network adapter can be created using the system's primary network interface.

  • Cluster filesystem creation—Before the filesystem can be created you must create the volumes where it will be placed. Do this with either Solstice DiskSuite or VxVM software. If VxVM software is chosen, the Veritas disk group created must be registered with the cluster before the filesystem is created.

  • Cluster filesystem mounting—The mount point directory needs to be created on all nodes before it will mount. The mount operation only needs to be performed once and can be performed from any cluster node.

  • Virtual hostname resource—An entry must exist in a name service or /etc/hosts on each node. Also, at least one NAFO group must exist on each node.

  • Resource type registration—The data agent package needs to be installed on both cluster nodes. The registration command can be run on any active cluster node in the cluster.

  • Resource Group creation—This can be performed on any active node once all the resources, that the group is comprised of, are created.

Script Sequence for HA-NFS Agent

A helpful technique, to determine the correct sequence to run your script commands in, is by mapping out what operations need to performed on each cluster node. FIGURE 2 shows the steps required on each cluster node to setup the HA-NFS data service. As noted in FIGURE 2, the dotted arrows show dependencies.

FIGURE 2 Data Service Setup Tasks and Dependencies for HA-NFS

The steps listed in FIGURE 2 above the top arrow are independent of each other and can be performed on either cluster node at any time. However, since it makes sense to execute all the commands without dependencies on the first node before a script is run on the second cluster node, FIGURE 2 presents the steps that way. This eliminates the need to go back and forth between the cluster nodes when the scripts are run.

Determining the Status of the Cluster

Included in any script should be a status check of the cluster current configuration to prevent the script from producing undesired results and to inform the user that the cluster is not in the state that the script assumes it to be in. The scstat -n command is a convenient way to determine whether the cluster nodes are active or online. It can also be used as a way to capture the names of the cluster nodes for use later in a script. The following is the output of the scstat -n command when it is run from the command line.

# scstat -n
-- Cluster Nodes --
        Node name    Status
        ---------    ------
 Cluster node: alpha      Online
 Cluster node: beta      Online

A shell script can be created to fetch the names of the cluster nodes and their current status, as shown in the following example.

STAT='scstat -n | awk '/^ Cluster node:/ {print $3,$4}''
NODE1='echo $STAT | cut -d" " -f1'
NODE1STAT='echo $STAT | cut -d" " -f2'
NODE2='echo $STAT | cut -d" " -f3'
NODE2STAT='echo $STAT | cut -d" " -f4'

Shared Storage Configuration

When the Solaris OE initializes, all devices physically connected to the system it is running on are probed, then mapped to logical device names. Working with logical device names, in the format of controller-target-disk-slice, is easier than referencing the physical path to the device, which can be very cryptic. However, the order in which devices are probed is determined by which bus slot the device controller is placed in and how the device is cabled.

While differences in logical device names do not have any ill effects, they must be taken into consideration when developing automated scripts since you cannot assume logical device names are always consistent between different clusters even if the hardware components are identical. To determine what the actual physical device is by examining its logical device name the luxadm command is useful. The following is an example of the output from this command.

# luxadm inquiry /dev/rdsk/c1t0d0s0

 Physical path:
Vendor:           SUN 
Product:          T300
Revision:          0116
Serial Number        9717E44007
Device type:        0x0 (Disk device)

From the output you can determine what type of storage device is assigned to a particular logical device name. If the shared storage is a Sun StorEdge T3 array, the associated logical device name can be extracted by examining all the device names appearing in the /dev/rdsk directory, searching for a product type of T300.

The following shell script routine can be used to search for the two entries in /dev/rdsk that match the product type of T300, the name Sun Microsystems uses to denote the Sun StorEdge T3 array.

find_T3() {
    ALL_DISKS='scdidadm -l | awk '{print $2}' | cut -d: -f2'
    for i in $ALL_DISKS
      DISKTYPE='luxadm inquiry ${i}s0 2>/dev/null \
| awk '/Product:/ {print $2}''
      if [ "$DISKTYPE" = "T300" ]; then
        CANDIDATES="$CANDIDATES 'basename $i'"
    NDISK='echo $CANDIDATES | wc -w'
    if [ $NDISK != "2" ]; then
        gettext "ERROR: The number of T3 arrays found \
is $NDISK \n"
        gettext "Number of T3 arrays must = 2\n"
        exit 1
    T3DISK1='echo $CANDIDATES | awk '{print $1}''
    T3DISK2='echo $CANDIDATES | awk '{print $2}''

Once the logical device name is determined, mirrored volumes can be created using either VxVM software or Solstice DiskSuite as described in the next section.

Creating a Shared Mirrored Volume with VxVM Software

The steps for creating a shared mirrored volume with VxVM software are:

  1. Initialize the disks.

  2. Create a disk group.

  3. Add the shared disk to the disk group.

  4. Create the mirrored volume.

  5. Register the disk group with the cluster.

The following commands are used to perform these steps. The variables T3DISK1 and T3DISK2 are used to represent the two Sun StorEdge T3 arrays. The values for these two variables are obtained using the code in the find_T3() example.

/etc/vx/bin/vxdisksetup -i $T3DISK1
/etc/vx/bin/vxdisksetup -i $T3DISK1
vxdg init mydskgrp $T3DISK1
vxdg -g mydskgrp adddisk $T3DISK2
vxassist -g mydskgrp make hanfsvol1 500m layout=mirror
scconf -a -D type=vxvm,name=mydskgrp,nodelist=$NODE1:$NODE2

After the shared storage is mirrored and registered with the cluster, you can create a filesystem on the mirrored volume as shown in the following command.

newfs /dev/vx/rdsk/mydiskgrp/hanfsvol1

Creating Shared Mirror Storage with Solstice DiskSuite

Since Solstice DiskSuite disksets, are cluster-aware the equivalent of VxVM disk groups, do not need to be registered with the cluster. However, disksets are created specifying the Disk ID (DID) numbers used to identify global devices instead of logical device names. To view all the logical device names to DID mappings, the scdidadm command with the -L option is run (see the following illustration).

# scdidamd -L
1 alpha:/dev/rdsk/c0t6d0 /dev/did/rdsk/d1
2 beta:/dev/rdsk/c2t0d0 /dev/did/rdsk/d2
2 alpha:/dev/rdsk/c1t0d0 /dev/did/rdsk/d2
3 beta:/dev/rdsk/c1t1d0 /dev/did/rdsk/d3
3 alpha:/dev/rdsk/c2t1d0 /dev/did/rdsk/d3
4 alpha:/dev/rdsk/c3t1d0 /dev/did/rdsk/d4
5 alpha:/dev/rdsk/c3t0d0 /dev/did/rdsk/d5
6 beta:/dev/rdsk/c0t6d0 /dev/did/rdsk/d6
7 beta:/dev/rdsk/c3t0d0 /dev/did/rdsk/d7
8 beta:/dev/rdsk/c3t1d0 /dev/did/rdsk/d8

Before an Solstice DiskSuite diskset can be created, the logical device names of the shared storage devices need to be translated into the equivalent DID device number. Using the function find_T3() (shown in a previous example), you can find the logical device names, then convert them to the equivalent DID device name by inserting the following lines into your script.

DID1='scdidadm -l | grep $T3DISK1 | awk '{print $3}''
DID2='scdidadm -l | grep $T3DISK2 | awk '{print $3}''

The steps for creating a mirrored volume using Solstice DiskSuite software are:

  1. Create a cluster disk group specifying the potential cluster node owners.

  2. Add the two Solstice DiskSuite T3 Arrays to the cluster disk group.

  3. Initialize the two Solstice DiskSuite T3 Arrays.

  4. Create a disk mirror.

  5. Add the two Solstice DiskSuite T3 Arrays to the mirror.

The following example shows the commands that perform these operations.

metaset -s mydskset -a -h $NODE1 $NODE2
metaset -s mydskset -a $DID1 $DID2
metainit -s mydskset mydskset/d0 1 1 ${DID1}s0
metainit -s mydskset mydskset/d1 1 1 ${DID2}s0
metainit -s mydskset mydskset/d100 -m mydskset/d0
metattach -s mydskset mydskset/d100 mydskset/d1
metaset -s mydskset -a -m $NODE1
metaset -s mydskset -a -m $NODE2

You can now create the filesystem as shown in the following example.

newfs /dev/md/mydskset/rdsk/d100

Mounting the Global Filesystem

After a global filesystem is created on the mirrored shared storage devices, the mount command can be run from any cluster node. However, before the mount can take place, a mount directory must be created on each cluster node and the entry that performs the mount must exist in each cluster nodes's /etc/vfstab file. The following example shows the commands run on each cluster node to perform these operations.

On beta:

mkdir /global/nfs
echo "/dev/vx/dsk/mydskgrp/hanfsvol1 \
/dev/vx/rdsk/mydskgrp/hanfsvol1 /global/nfs ufs 2 yes \ global,logging" >> /etc/vfstab

On alpha:

mkdir /global/nfs
echo "/dev/vx/dsk/mydskgrp/hanfsvol1 \
/dev/vx/rdsk/mydskgrp/hanfsvol1 /global/nfs ufs 2 yes \ global,logging" >> /etc/vfstab
mount /global/nfs

Once the global filesystem is mounted, application software can be placed in it and administrative directory and files can be created there. For the HA-NFS example, no additional application software is required, but you need to create some additional directories and configuration files as shown in the following example.

On beta:

mount /global/nfs
mkdir /global/nfs/admin
mkdir /global/nfs/admin/SUNW.nfs
echo 'share -F nfs -o rw -d"HA-NFS" /global/nfs/data' > \
mkdir /global/nfs/data
chmod 777 /global/nfs/data

Creating the Data Service Resource Group

When a data service failure is detected on an active cluster node, the data service is transferred, or failed-over, to a working cluster node. The failover unit that Sun Cluster 3.0 software uses is the resource group, which is a collection of resources that are required for the data service to run. Resources are categorized by their type. For example, the resource that represents the NFS data service is of type SUNW.nfs and the resource for failing-over the shared storage device is of type SUNW.HAStorage. Before a resource can be created, you need to register its type.

A logical hostname resource is required for all data services since this name represents the IP address clients use to access the service and must be transferable from one cluster node to another. Although it is considered a resource, no resource type is associated with it. Therefore, there is no resource type that needs to be registered with the cluster.

The basic steps to create a resource group for a data service are:

  1. Register the resource types of the resources used in the group, if not already registered.

  2. Create a resource group specifying the cluster nodes that can run it along with the pathname of any administrative directory.

  3. Add required resources to the resource group.

  4. Place the resource group in the online mode.

The following example illustrates those steps.

On beta:

scrgadm -a -t SUNW.nfs
scrgadm -a -t SUNW.HAStorage
scrgadm -a -g myresgrp -h alpha,beta -y \
scrgadm -a -L -g myresgrp -l hostname
scrgadm -a -j hares -g myresgrp -t SUNW.HAStorage -x \
ServicePaths=/global/nfs -x AffinityOn=True
scrgadm -a -j nfsres -g myresgrp -t SUNW.nfs -y \
scswitch -Z -g myresgrp
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020