Sunday 27 July, 2008 - 19:15
eth1 NIC failed on padstow1 causing the padstow2 node to drop out of the cluster. (padstow1 was booted first and padstow2 was booted next)
Used VMware to connect the eth1 NIC on padstow1 image
On padstow2,:
$ORA_CRS_HOME/bin/crsctl start crs
$ORA_CRS_HOME/bin/crsctl check crs
$ORA_CRS_HOME/bin/crsctl start resources
This restarted the Cluster Ready Services (CRS) stack. The check was to see when the stack was available. Once it was done, all of the dependent resources were started.