Cisco Cisco Prime Central 1.2 Guía De Instalación
11
3
Installing Prime Central and an Embedded Database in a Local
Redundancy HA Configuration
Installing Prime Central in an RHCS local HA configuration is a three-part process:
1.
Install RHEL 5.8 on both nodes.
2.
Use multipath shared storage and install Prime Central on node 1.
3.
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
Local Cluster Service Failure
Name: Service failure.
Purpose: Test the service startup after
a failure occurs.
a failure occurs.
1.
Simulate a service failure by stopping its
processes or shutting down the Oracle
listener.
processes or shutting down the Oracle
listener.
2.
Verify that the service restarts on the same
node where it was running.
node where it was running.
3.
Check the log for errors.
4.
Test both the Prime Central and Oracle
services.
services.
The service is restarted on the same
node.
node.
Local Cluster Hardware Failure
Name: Stop node with fencing off.
Purpose: Verify that the node requires
manual fencing after the other node,
including its fencing agent, is
removed.
manual fencing after the other node,
including its fencing agent, is
removed.
1.
Disconnect the fencing agent from one of
the nodes, then power it off.
the nodes, then power it off.
2.
Observe the other node behavior.
3.
Check the log for errors and the request
for manual fencing.
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.
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.
function when the other node does
not exist or has no power.
1.
Power down both nodes.
2.
Disconnect the fencing agent from one of
the nodes.
the nodes.
3.
Start the other node. It attempts to fence
the other node, but fails with the regular
fencing agent. Manual fencing is required.
the other node, but fails with the regular
fencing agent. Manual fencing is required.
4.
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.
(and does not show in the clustat
command) before acknowledging that
manual fencing is performed.
Table 4
Local Redundancy Verification Tests (continued)
Description
Procedure
Expected Results