Using the Sun Cluster command-line interface, perform a fail over to the second node.
For example:
# /usr/cluster/bin/scswitch -z -g CAL-CS1-RG -h Node2
Edit the configuration file, ics.conf, by adding the parameters shown in the example that follows.
Back up the ics.conf file before starting this step.
! The following changes were made to configure Calendar Server ! Highly Available ! local.server.ha.enabled="yes" local.server.ha.agent="SUNWscics" service.http.listenaddr="IPAddressCS1" local.hostname="LOG-HOST-CS1-RS" local.servername="LOG-HOST-CS1-RS" service.ens.host="LOG-HOST-CS1-RS" service.http.calendarhostname="LOG-HOST-CS1-RS-Domain.com" local.autorestart="yes" service.listenaddr = "IPAddressCS1"
The expected value for service.http.calendarhostname is a fully qualified hostname.
Using the Sun Cluster command-line interface, create the Calendar Server resource group.
Create a calendar resource group and enable it.
For example:
./scrgadm -a -j CAL-SVR-CS1-RS -g CAL-CS1-RG -t SUNW.scics -x ICS_serverroot=/cal-svr-baseCS1 -y Resource_dependencies=CAL-HASP-CS1-RS,LOG-HOST-CS1-RS ./scrgadm -e -j CAL-SVR-CS1-RS
Using the Sun Cluster command-line interface to test the successful creation of the Calendar Server resource group, perform a fail over to the first node, which is the Primary node.
For example:
./scswitch -z -g CAL-CS1-RG -h Node1