ClusterWare service Introduction

ClusterWare service Introduction 1. terware startup flowchart 2. Agent process started by ClusterWare layer proxy process description Orarootagent is responsible for managing the first layer of ohasd proxy process for all ohasd resources owned by root users ohasd Cssdagent CSSD proxy process (with it to generate the CSSD process) oraagent manages the proxy process of ohasd resources owned by all oracle users. Cssdmonitor monitors the health status of cssd and nodes together with cssdagent. Orarootagent CRSD manages Layer 2 of the CTSSD cluster time synchronization service process, which is the main process of resources last year. diskmon disk monitoring process ACFS Drivers ASM Cluster File System driver Cssdagent CSSD cluster synchronization service process Oraagent mdnsd dns lookup resource EVMD event monitoring process ASM monitoring ASM Example of resource GIPCD inline integration and inner connection point communication use resources GPNPD plug-and-play master process Cssdmonitor cssdmonitor cssd process monitoring process layer-3 CRSD oraagent is responsible for managing all the crsd resources of all oracle users the orarootagent is responsible for managing all the crsd resources of the root user. The proxy process oraagnet ASM Resource ASM instance resources Diskgroup is used to manage, monitor the Resource DB Resource used by the ASM disk, and manage the database and instance usage. resource SCAN Listener resource Listener node Listener Resource services monitoring and management resources used by Services ONS Oracle Notification Service eONS enhanced Oracle notification service layer-4 GSD backward compatible with 9i resources oraroottagent Network Resourc E monitoring public network resources scan vip resources node vip each NODE has a VIP resource ACFS Registry load ACFS resources gns vip resources III. background processes constitute the main processes of the high availability service layer process summary Grid Plug and Play (GPNPD) grid plug-and-play helps you quickly add cluster nodes to the cluster Grid Interprocess Communication. The daemon can use redundant NICs as internal links (GIPC) multicast Domain Name Service is used for GPnp to search for the profile in the cluster, and also for GNS to perform Name resolution. This process is a background process in Linux and UNIX. On Windows, it is a Grid Command Service for Oracle Grid Naming Service, which is used to automatically allocate scan vip and node VIP to the cluster. (GNS) parsing SCAN names and other work Cluster Time Synchronization the Time between Cluster nodes should be synchronized. In 11gR2, Clusterware Service (CTSS) provides the CTSS Service, it can ensure that the time of all nodes in the cluster is synchronized. If no NTP service is found during cluster configuration, the CTSS is configured by default during installation. The Cluster Ready Services (CRS) CRS daemon CRSD manages each Cluster resource stored in OCR, including startup, stop, monitoring, and failover. When the resource status changes, the CRSD process generates an event. When a RAC node is loaded in, the CRSD process starts to monitor resources such as instances and listeners corresponding to the node; when these components fail, CRS automatically restarts their Cluster Synchronization Services 1. CSS controls the node members in the Cluster and manages Cluster configurations by sending notifications. (CSS) if a third-party cluster software is used, the CSS process layer uses the third-party cluster software to manage cluster node configuration 2. The cssdagent process monitors the cluster and provides I/O protection. This service was previously provided by oprocd and OraFenceService in Windows. Cssdagent failed to run. Clusterware will restart ASM to provide Clusterware disk file storage. The ASM instance needs to be started before the cssd process starts and MOUNT the corresponding disk group to a background process, events created by Clusterware are released, which serves as the communication bridge between CRS and CSS.