Here is the Oracle 11gR2 clusterware

startup sequence:
ohasd -> orarootagent -> ora.cssdmonitor : Monitors CSSD and node health (along with the
cssdagent). Try to restart the node if the node is unhealthy.
-> ora.ctssd : Cluster Time Synchronization Services Daemon
-> ora.crsd -> oraagent -> ora.LISTENER.lsnr
-> ora.LISTENER_SCAN.lsnr
-> ora.ons
-> ora.eons
-> ora.asm
-> ora.DB.db

->orarootagent -> ora.nodename.vip

-> ora.net1.network
-> ora.gns.vip
-> ora.gnsd
-> ora.SCANn.vip

-> cssdagent -> ora.cssd : Cluster Synchronization Services

-> oraagent -> ora.mdnsd : Used for DNS lookup
-> ora.evmd
-> ora.asmd
-> ora.gpnpd : Grid Plug and Play = adding a node to the cluster is easier (we
need less configuration for the new node)

If a resource is written using blue & bold font => resource owned by root. The other resources
are owner by oracle. (all this on UNIX environment)
When a resource is managed by root, we need to run the command crsctl as root or oracle.
When Clusterware starts three files are involved.
OLR - Is the first to be read and opened. This file is local and this file contains information where is stored voting disk,
and information to startup the ASM. (e.g ASM DiscoveryString)

VOTING DISK - This is the second file to be opened and read, to read the voting file only depend on the OLR be
accessible. ASM start after CSSD or ASM does not start if CSSD is offline (i.e voting file missing)

How Voting Disk are stored in ASM?

Voting disks are placed directly on ASMDISK. Oracle Clusterware will store the votedisk on the disk within a disk group
that holds the Voting Files.
Oracle Clusterware does not rely on ASM to access the Voting Files, that’s means wich Oracle Clusterware does not need
of Diskgroup to read and write on ASMDISK.
You only know if exist a voting files in a ASMDISK (v$asm_disk using column VOTING_FILE). So, voting files not depend of
Diskgroup to be accessed, does not mean that, we don’t need the diskgroup, diskgroup and voting file are linked by their
settings.

OCR - Finally the ASM Instance starts and mount all Diskgroups, then Clusterware Deamon (CRSD) open and read the
OCR which is stored on Diskgroup.