Search <book_title>...

InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - Solaris

Last Published: 2025-04-18

Product(s): InfoScale & Storage Foundation (9.0)

Platform: Solaris

Sample configuration file for removing a node from the cluster

You may use this sample file as reference information to understand the configuration changes involved when you remove a node from a cluster.

The existing sample configuration before removing the node sys3 is as follows:

The existing clusterclus1comprises three nodes sys1, sys2, and sys3 and hosts a single database.
The database is stored on CFS.
The database is managed by a VCS database agent.
The agent starts, stops, and monitors the database.

Note:

The following sample file shows in bold the configuration information that is removed when the node sys3 is removed from the cluster.

include "types.cf"
include "CFSTypes.cf"
include "CVMTypes.cf"

cluster clus1 (
        UserNames = { admin = bopHo }
        Administrators = { admin }
        UseFence = SCSI3
        )

system sys1 (
        )
system sys2 (
        )
system sys3 (
       )

Note:

In the following group app_grp, the sys3 node must be removed.

group app_grp (
        SystemList = { sys1 = 0, sys2 = 1, sys3 = 2 }
        AutoFailOver = 0
        Parallel = 1
        AutoStartList = { sys1, sys2, sys3 }
        )

Note:

In the following application resource, the sys3 node information must be removed.

App app1 (
										Critical = 0
										Sid @sys1 = vrts1							
								  Sid @sys2 = vrts2
          Sid @sys3 = vrts3
          )

CFSMount appdata_mnt (
         Critical = 0
         MountPoint = "/oradata"
         BlockDevice = "/dev/vx/dsk/appdatadg/appdatavol"
         )

CVMVolDg appdata_voldg (
         Critical = 0
         CVMDiskGroup = appdatadg
         CVMVolume = { appdatavol }
         CVMActivation = sw
         )

requires group cvm online local firm
app1 requires appdata_mnt
appdata_mnt requires appdata_voldg

Note:

In the following CVM and CVMCluster resources, the sys3 node information must be removed.

group cvm (
        SystemList = { sys1 = 0, sys2 = 1, sys3 =2}
        AutoFailOver = 0
        Parallel = 1
        AutoStartList = { sys1, sys2, sys3 }
        )

        CFSfsckd vxfsckd (
                )



        CVMCluster cvm_clus (
              CVMClustName = clus1
              CVMNodeId = { sys1 = 0, sys2 = 1, sys3 =2 }
              CVMTransport = gab
              CVMTimeout = 200
              )


       CVMVxconfigd cvm_vxconfigd (
               Critical = 0
               CVMVxconfigdArgs = { syslog }
               )

vxfsckd requires cvm_clus
cvm_clus requires cvm_vxconfigd