Cisco Cisco Prime Central 1.1 Guia Da Instalação

After the Prime Central service is running in an HA cluster, you cannot restart its components (such as the portal, 
integration layer, and database) without first freezing the cluster. After you restart the component, you can unfreeze the 
cluster. 

For example, attaching or detaching a domain manager to or from Prime Central requires an integration layer restart. 
On the active node, freeze the HA cluster, restart the integration layer, and unfreeze the cluster:

# clusvcadm -Z Prime-Central-service-name

# su - primeusr

# itgctl stop

# itgctl start

# exit

# clusvcadm -U Prime-Central-service-name

The following table lists the parameters in the /etc/cluster/cluster.conf file for which you must set unique values.

On both nodes, check the status of the cluster:

# clustat

The output is similar to the following:

Cluster Status for bm1cluster @ Thu Jun 21 23:58:35 2012

Member Status: Quorate

Member Name                  ID    Status

------ ----                  ----  ------

prime-ha-node1.cisco.com     1     Online, Local, rgmanager

prime-ha-node2.cisco.com     2     Online, rgmanager

Service Name                  Owner (Last)                  State         

------- ----                  ----- ------                  -----         

service:vmpcservice           prime-ha-node2.cisco.com      started

Complete the following steps on both nodes, except where noted:

Configure cman, rgmanager, and ricci to start automatically upon bootup:

# chkconfig cman on

Cluster name

bm1cluster

—

Multicast address

224.0.0.251

The multicast address must be unique per subnet and must be 
working before you start your cluster. For a tool to verify that your 
multicast address is correct, see 

Service IP address

192.168.1.130

—

First node name

prime-ha-node1.cisco.com

—

Second node name

prime-ha-node2.cisco.com

—

Shared partition path

/dev/mapper/mpath2p1

—