Cisco Cisco Prime Central 1.2 Installation Guide

Installing Prime Central in an RHCS local HA configuration is a three-part process:

Install RHEL 5.8 on both nodes.

Use multipath shared storage and install Prime Central on node 1.

Configure and enable clustering so that Prime Central can relocate between nodes.

The examples provided use the following hostnames and IP addresses; yours will be different:

Node 1—prime-ha-node1.cisco.com (192.168.1.110)

Node 2—prime-ha-node2.cisco.com (192.168.1.120)

Virtual IP address—prime-service.cisco.com (192.168.1.130)

Gateway—192.168.1.1

Domain Name System (DNS)—192.168.1.2

Name: Service failure.

Purpose: Test the service startup after 
a failure occurs.

Simulate a service failure by stopping its 
processes or shutting down the Oracle 
listener.

Verify that the service restarts on the same 
node where it was running.

Check the log for errors.

Test both the Prime Central and Oracle 
services.

The service is restarted on the same 
node.

Name: Stop node with fencing off.

Purpose: Verify that the node requires 
manual fencing after the other node, 
including its fencing agent, is 
removed.

Disconnect the fencing agent from one of 
the nodes, then power it off.

Observe the other node behavior.

Check the log for errors and the request 
for manual fencing.

The fence_ack_manual required 
notification appears in the log files. 
The cluster is running with one node 
and all services running on it.

Name: Single-node cluster.

Purpose: Verify that the cluster can 
function when the other node does 
not exist or has no power.

Power down both nodes.

Disconnect the fencing agent from one of 
the nodes.

Start the other node. It attempts to fence 
the other node, but fails with the regular 
fencing agent. Manual fencing is required.

Acknowledge the manual fencing.

The cluster does not start the services 
(and does not show in the clustat 
command) before acknowledging that 
manual fencing is performed.