12 - Cluster Hooks Revisited

Abstract

After the cluster has been created, it is essential to change the file system hierarchy system. The first change is made in the location of the file system. The files, which are required by the member to boot the system, are located in the boot partition directory. Each member in a cluster has its own boot partition that is mounted at /cluster/members/member/boot_partition. Both member-specific and cluster common files are used. In a cluster, hardware management is unchanged from a stand-alone system. A minor change occurs when a cluster is first created. Some of the databases that were previously located in the /etc directory are relocated to each cluster member's boot partition. “hwmgr” is a cluster-aware command. It always focuses on the cluster member. In a cluster there are multiple systems generating events. Before TruCluster Server, 5.0A version events generated in a cluster were member-specific. In a cluster, events are logged in to a particular member or entire cluster. The event attribute cluster_event is set to true, which generates the event clusterwise. Additional event templates are added to the TruCluster Server specific system when TruCluster Server is installed. The Event Manager (EVM) filter added can be seen by using evf script. There are two cluster events on a stand-alone system. On a cluster, there are forty-seven cluster events. Link Aggregation (LAG) is used on a network interface that is not associated with Local Area Network (LAN) cluster interconnect. Events can be filtered by the member's hostname with the evmget, evmshow and evmwatch commands.