Cisco Prime Central 1.4 HA Guide

RHCS Components and Functionality

RHCS is included with the Red Hat Enterprise Linux 5.8/6.5 (RHEL 5.8/6.5) Advanced Program and has the following components:

• Cluster infrastructure—Basic functions that enable a group of computers (nodes) to work together as a cluster. The RHCS cluster infrastructure performs cluster management, lock management, fencing, and cluster configuration management.
• High availability service management—Failover of services from one cluster node to another when a node becomes inoperative.
• Cluster administration tools—Configuration and management tools for setting up, configuring, and managing a Red Hat cluster, including cluster infrastructure components, high availability service management components, and storage.

Supported RHCS Fencing Options

A fencing device cuts off a node from shared storage to ensure data integrity. The supported fencing options are:

• fence_ilo —Cisco validated Prime Central HA with the HP Integrated Lights-Out (HP iLO) fence_ilo automatic fencing method; other automatic fencing methods can be used but have not been validated.
• fence_manual —Assigns the manual fencing agent. This fencing agent is temporary; you should not use it in production because it does not perform automated actions. If a cluster problem occurs, you must manually disconnect the node and storage, or use another fencing agent to disconnect them. If you choose this option during the installation because you want to add a different Red Hat-supported fencing device, use the RHCS GUI to provision the device after installation. Be sure to add it as the main fencing method, and move the manual fencing agent to the backup method, as shown in Figure 1-2 and Figure 1-3.

Note the following:

• In Figure 1-2, the HP iLO host 1 is 192.168.1.10.
• In Figure 1-3, the HP iLO host 2 is 192.168.1.11.
• To prevent fencing loops, the cluster interconnect and power fencing (for example, HP iLO) should use the same network, such as bond0.
• If the main fencing device is a remote power switch, define all ports that simultaneously supply power to the node.

Note For general information about the RHCS web GUI, see Verifying the Prime Central RHCS HA Installation. For complete information about using the RHCS web GUI, see the Red Hat Conga User Guide. For information about provisioning and managing dual-node cluster fencing devices, see the RHCS user documentation.

Figure 1-2 RHCS GUI Fencing Method Window—Node 1

Figure 1-3 RHCS GUI Fencing Method Window—Node 2

The fencing methods shown in Figure 1-2 and Figure 1-3 change the following sections in the cluster.conf file:

RHCS HA Local Redundancy Requirements

We strongly recommend that you use a hardware installation designed to avoid a single point of failure. See Figure 1-4.

Figure 1-4 Local Redundancy Hardware Installation Designed to Avoid a Single Point of Failure

Configuring Hardware for Prime Central RHCS Local Redundancy HA

Figure 1-5 shows the recommended hardware configuration for Prime Central RHCS local redundancy HA.

Figure 1-5 Prime Central Dual-Node Cluster for Local Redundancy HA

Configure the external storage so all disks and logical unit numbers (LUNs) are accessible from both servers in the cluster. The disk and LUN configuration depends on the storage type:

• If you are using JBOD disks, provide enough physical disks to create the volumes listed in Table 1-2 to satisfy the Oracle performance requirements.
• If you are using storage that supports hardware RAID, divide the physical disks into LUNs so that the volumes listed in Table 1-2 can be created and configured to satisfy the Oracle performance requirements and can be protected with RAID5, RAID1, or RAID10. The Oracle volumes can be created on a single LUN.

Configuring the OS for Prime Central Local Redundancy HA Managed by RHCS

1. Install the OS and all recommended patches on both servers in the cluster. Installations on both servers must be identical.

2. Verify that access is available to all external disks.

3. Create the internal disk partitions listed in Table 1-3 . Placing the individual directories in separate partitions is recommended, but not required.

4. Complete the internal disk partitions for both servers.

5. Keep the nodes synchronized:

Installing the Red Hat Cluster Service

Using the procedures in the Red Hat user documentation, install RHEL 5.8/6.5 with the RHCS. When you set up the RHCS disk groups and volumes, keep the following in mind:

• All of the shared storage should have an ext3 file system installed and a label set.
• Shared storage must be accessible from all cluster nodes.

Verifying the Prime Central RHCS HA Installation

Before You Begin

• Verify that your system meets all the hardware and software requirements in “Installation Requirements” in the Cisco Prime Central 1.4 Quick Start Guide.
• Set up two nodes that have:

– Static IP addresses and hostnames that are registered correctly in the DNS.

– The same root password, which cannot contain a percent sign (%, ^, $, *).

• Set up one virtual IP address and hostname that are registered correctly in the DNS. In this section, the virtual IP address is 192.168.1.130.
• Set up shared storage that is compatible with RHEL device-mapper (DM) multipath and cluster fencing.
• Install RHEL 5.8/6.5 on both nodes.
• If the default folder location and names are changed, look for the section “Require Manual Definition” to make corresponding changes in the below mentioned files:

– /root/ha-stuff/pc/PrimeCentral.sh

– /root/ha-stuff/pc/UninstallPrimeCentral.sh

– /usr/local/bin/pc.sh

– /usr/local/bin/createUserGroup.sh

Adding Clustering to the Installed Red Hat Server

To add clustering to the newly installed Red Hat server, complete the following steps in parallel on both nodes, except where noted:

Step 1 Create local directories named /rhel and /cdrom.

Step 2 Copy the.iso file that was used for the virtual machine (VM) RHCS installation to the /rhel directory.

Step 3 Mount the /rhel.iso file to /cdrom:

Note To permanently mount the drive, update the /etc/fstab file. See http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/4/html/Introduction_To_System_Administration/s2-storage-mount-fstab.html.

Step 4 Create a file named /etc/yum.repos.d/local.repo. Use UNIX format and be sure there are no spaces before lines.

Step 5 Save the newly created file in local.repo, as follows:

Step 6 Install the clustering package:

Step 7 Add the information for both nodes to the /etc/hosts file; for example:

Step 8 Generate a Secure Shell (SSH) key for the root user:

Step 9 (On the first node only) Share the node’s public key with the other node so that dynamically creating a secure shell between the nodes does not prompt for a password:

Step 10 Verify that the.ssh directory has 700 permission and the.ssh/id_rsa file has 600 permission:

Step 11 Verify that your SSH is working without an authentication or password prompt:

Caution The Prime Central service will not start if SSH prompts for authentication or a password. Be sure to complete all of the following substeps.

---

a. On node prime-ha-node1.cisco.com, enter:

b. On node prime-ha-node2.cisco.com, enter:

c. If you are prompted for a password, check the permissions of all folders and files that you modified in the preceding steps.

d. If you are prompted to continue connecting, enter yes. (The prompt should appear only the first time you use SSH to connect to the node.)

Step 12 Verify that the virtual IP address is accessible from outside the cluster’s subnet:

Step 13 On a computer outside the cluster’s subnet, ping the virtual IP address:

If you do not get a valid response, determine which part of the OS or network setup is blocking.

Adding Shared Partitions

To add shared partitions, complete the following steps in parallel on both nodes, except where noted:

Note The examples provided use device mapping names such as mpath2 and mpath2p1; yours will be different.

Step 1 Set up multipath:

Step 2 Check for available disks:

In the output, note mpath2, which is the multipath virtual device or disk that you will use later as shared storage.

Note If you previously set up a partition on the disk, you might see output such as mpath2p. You must delete that partition before proceeding to the next step.

Step 3 (On the first node only) Create a 100-GB, shared partition:

Step 4 Reboot both nodes.

Step 5 Check for new partitions:

Step 6 (On the first node only) Format the new shared partition:

Step 7 Create target locations:

Step 8 Verify that both nodes can mount and unmount the shared storage:

a. On the first node, mount the shared storage and save a file that contains only the value 1 to the shared storage. The test.txt file should exist in the list of contents of /opt/pc:

b. On the second node, mount the shared storage and verify that the test.txt file exists and contains the value 1 :

If you cannot mount or unmount the shared storage, or if the test.txt file does not exist when you mount it to the second node, your multipath is not set up correctly.

Accessing and Distributing the Prime Central.tar File

Step 1 Insert the Cisco Prime Central 1.4 USB, navigate to the High Availability/RHCS Bare Metal Local HA/Prime Central folder, and locate the primecentral_v1.4_ha_vm.tar.gz file.

Step 2 Use SSH to connect to the first node.

Step 3 Copy the primecentral_v1.4_ha_vm.tar.gz file to the first node.

Step 4 Back up the following directories on both nodes:

• /root/ha-stuff/pc
• /usr/local/bin

Step 5 Distribute the file:

Step 6 Navigate to the Base Application folder and copy primecentral_v1.4.bin and all available zip files into the /root/ha-stuff/pc directory:

Installing Prime Central on the First Node in an HA Setup

To install Prime Central on the first node only:

Step 1 Mount the shared partitions:

Step 2 Add a virtual IP cluster service address for the Prime Central service:

Step 3 Update the install.properties file and verify that all required properties have values. Review the comments at the top of the install.properties file for details.

Note To install Prime Central silently, you must edit the /root/ha-stuff/pc/install.properties file. See “Sample install.properties Files” in the Cisco Prime Central 1.4 Quick Start Guide.

Step 4 Install Prime Central:

Note You run the PrimeCentral.sh script by adding the preceding command-line parameters. If you do not add the command-line parameters, you are prompted for the required data.

Step 5 In another terminal window, check the installation process:

Step 6 After the installation succeeds, start Prime Central:

Step 7 Verify that Prime Central is running correctly; then, stop it:

Step 8 Remove the virtual IP addresses:

Step 9 Unmount the shared partitions:

Setting Up the Prime Central Cluster Service

To set up and manage a cluster, you can use the CLI or the GUI. This section explains how to use the CLI. To use the GUI, see the Red Hat Enterprise Linux 5 Cluster Administration Guide, sections 3 and 4.

To set up the Prime Central cluster service, complete the following steps in parallel on both nodes, except where noted:

Step 1 Modify the /etc/cluster/cluster.conf file by setting unique values for the parameters listed in Table 1-5 .

Step 2 Copy the edited cluster.conf file to the /etc/cluster/ directory.

Whenever you modify the cluster.conf file, increment the config_version value so the cluster.conf file propagates correctly to the nodes. To propagate the cluster.conf file manually, you must stop the cluster, copy the file, and then start the cluster.

Step 3 Start the cluster services:

Enter each command on one node and then immediately enter the same command on the other node.

For example, when cman starts on a node, it waits for the other node to start cman. If the other node takes too long to start cman, cman times out on the first node.

Step 4 (For the RHCS luci GUI only) Using the username admin, start the RHCS ricci service:

Step 5 (For the RHCS luci GUI only) On the first node only, start the RHCS luci services:

Step 6 To test failover, relocate the service to another node:

Step 7 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 an application 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:

Modifying Parameters in the cluster.conf File

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

Checking the Cluster Services

On both nodes, check the status of the cluster:

The output is similar to the following:

Next Steps

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

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

Step 2 (On the first node only) Configure luci to start automatically upon bootup:

Step 3 Verify that the required ports are open. For a list of ports that Prime Central requires, see “Prime Central Protocols and Ports” in the Cisco Prime Central 1.4 Quick Start Guide.

Step 4 Enable the firewall:

Step 5 Disable Security-Enhanced Linux (SELinux):

Before You Begin

• Verify that your system meets all the hardware and software requirements in “Installation Requirements” in the Cisco Prime Central 1.4 Quick Start Guide.
• If you changed the default installation folder (/opt/primeusr/faultmgmt), make the equivalent changes in the following files (look for the section titled “Require manual definition” in each file):

– /usr/local/bin/fm.sh

– /images/fm_status.sh

Installing RHEL 6.5

To install RHEL 6.5, complete the following steps in parallel on both nodes, except where noted:

Step 1 Configure specialized storage devices, high availability, and virtualization. See the Red Hat documentation for instructions.

Step 2 Verify that the following options are checked:

• Virtualization: Virtualization Tools
• High Availability: High Availability
• Desktops: General Purpose Desktop
• Desktops: X Window System

Step 3 Create local directories named /rhel and /cdrom-6.5.

Step 4 Copy the.iso file that was used for the node installation to the /rhel directory.

Step 5 Mount the /rhel.iso file to /cdrom-6.5:

Note To permanently mount the drive, update the /etc/fstab file. See http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/4/html/Introduction_To_System_Administration/s2-storage-mount-fstab.html.

Step 6 Create a file named /etc/yum.repos.d/local.repo. Use UNIX format and be sure there are no spaces before lines.

Step 7 Save the newly created file in local.repo, as follows:

Step 8 (Optional) If you forget the HA package and want to install it later, enter:

Step 9 (Optional) If you forget the desktop and want to install it later, enter:

Then, change id:3:initdefault: to id:5:initdefault: and reboot the server.

Step 10 Temporarily disable the firewall and SELinux to enable initial testing of the cluster:

a. To disable the firewall, enter:

b. To disable SELinux, enter:

Step 11 Keep the nodes synchronized:

Step 12 Switch network daemons:

Step 13 Edit the /etc/hosts file to add the node information; for example:

Step 14 Generate an SSH key for the root user:

Step 15 (On the first node only) Share the node’s public key with the other node so that dynamically creating a secure shell between the nodes does not prompt for a password:

Step 16 Verify that the.ssh directory has 700 permission and the.ssh/id_rsa file has 600 permission:

Step 17 Verify that your SSH is working without an authentication or password prompt:

Caution The Fault Management service will not start if SSH prompts for authentication or a password. Be sure to complete all of the following substeps.

---

a. On node prime-ha-node1.cisco.com, enter:

b. On node prime-ha-node2.cisco.com, enter:

c. If you are prompted for a password, check the permissions of all folders and files that you modified in the preceding steps.

d. If you are prompted to continue connecting, enter yes. (The prompt should appear only the first time you use SSH to connect to the node.)

Configuring Multipath

To configure multipath, complete the following steps in parallel on both nodes, except where noted:

Note These steps set up a nonclustered drive. If you want to do a live migration of your virtual machines, you must set up a clustered drive such as the Clustered Logical Volume Manager (CLVM).

Step 1 Install multipath:

Step 2 Configure and start the services:

Step 3 Check for available disks. The names of the multipath disks must be identical on both nodes:

In the output, note mpathc, which is the multipath virtual device or disk that you will use later as shared storage.

Adding Shared Partitions

To add shared partitions, complete the following steps in parallel on both nodes, except where noted:

Note The examples provided use device mapping names such as mpathc and mpathcp1; yours will be different.

Step 1 (On the first node only) Create a 100-GB, shared partition:

Step 2 Reboot both nodes.

Step 3 Check for new partitions:

Step 4 Create target locations on both nodes:

Step 5 Check if the new partition is mapped to another server:

If the mount fails due to an invalid file type, the partition is not a link to an existing partition; skip to Step 6.

Otherwise, run a directory listing of /images. If the listing contains data from an existing partition, do not reformat this partition. Instead, leave this partition as is and return to Step 1 to create another partition.

Step 6 (On the first node only) Format the new shared partition:

Step 7 Verify that both nodes can mount and unmount the shared storage:

a. On the first node, mount the shared storage and save a file that contains only the value 1 to the shared storage. The test.txt file should exist in the list of contents of /images:

b. On the second node, mount the shared storage and verify that the test.txt file exists and contains the value 1 :

If you cannot mount or unmount the shared storage, or if the test.txt file does not exist when you mount it to the second node, your multipath is not set up correctly.

Setting Up the Prime Central Fault Management Virtual Machine

Step 1 Mount the newly created partition on the first node:

Step 2 (On the first node only) Add a new storage pool:

a. Run vncserver and use the VNC client to access the node.

b. Launch the virt-manager.

c. Click Edit Connection Details.

d. Click the Storage tab.

e. Click the + button to add a new storage pool.

f. In the Add a New Storage Pool: Step 1 of 2 window, enter fm_images as the storage pool name, choose fs: Pre-Formatted Block Device as the type, and click Forward.

g. In the Add a New Storage Pool: Step 2 of 2 window, verify that the settings are as follows; then, click Finish :

– Target Path: /images

– Format: auto

– Source Path: /dev/mapper/mpathcp1

Step 3 (On the first node only) Add a new storage volume:

a. In the virt-manager, click the Storage tab.

Caution Do not check the Autostart: On Boot check box.

---

b. Click the New Volume button.

c. In the Add a Storage Volume window, enter the following values; then, click Finish :

– Name: fm_vm (.img is appended)

– Format: raw

– Max Capacity (MB): Use all available storage space from the pool.

– Allocation (MB): 0

Step 4 Create a virtual network:

a. On each node, add a bridge to the host, to enable the virtual machines to use the same physical network as the nodes:

Add these lines and save:

Note The IPADDR has the same value as the node to which you are adding this file. This example is for node 1.

Add this line and save:

b. On each node, update the /etc/sysctl.conf file to allow forwarding to the virtual machines:

Step 5 Create a new virtual machine:

a. Copy the RHEL 5.8/6.5.iso file to the /rhel directory.

b. In the virt-manager window, click the create a new virtual machine button.

c. In the Step 1 of 5 window, enter fm_vm as the virtual machine name, click Local install media, and click Forward.

d. In the Step 2 of 5 window, click Use ISO image and specify the location of the RHEL 5.8/6.5.iso image. Verify that the OS type is Linux and the version is Red Hat Enterprise Linux 5.4 or later. Then, click Forward.

e. In the Step 3 of 5 window, enter the amount of RAM and CPUs to use for the virtual machine. For recommendations, see “Installation Requirements” in the Cisco Prime Central 1.4 Quick Start Guide. Then, click Forward.

f. In the Step 4 of 5 window, check Enable storage for this virtual machine. Click Select managed or other existing storage and browse to /images/fm_vm.img (which you created in Step 3 c ). Then, click Forward.

g. In the Step 5 of 5 window, verify that the settings are as follows; then, click Finish :

– Advanced options: Host device eth0 (Bridge 'br0')

– Virt Type: kvm

– Architecture: x86_64

Step 6 Install RHEL 5.8/6.5 on the new virtual machine. The OS library, kernel-headers, is required; choose the Software Development option when installing RHEL to ensure that the kernel-headers library is installed.

Step 7 Temporarily disable the firewall and SELinux to enable initial testing of the cluster:

a. To disable the firewall, enter:

b. To disable SELinux, enter:

Step 8 Update the /etc/hosts file on the virtual machine:

For example:

Step 9 From the virtual machine, ping both nodes. If the ping fails, add both nodes to the virtual machine’s /etc/hosts file. For example:

Step 10 Save the /etc/hosts file; then, run the following tests:

If any of the tests return incorrect results, check the /etc/hosts file for typos. Also check the /etc/sysconfig/network file and verify that the HOSTNAME entry contains your server’s FQDN (fm-service.cisco.com in this example).

Step 11 Generate an SSH key for the virtual machine’s root user and share it with both nodes:

Step 12 On the virtual machine, verify that the.ssh directory has 700 permission and the.ssh/id_rsa file has 600 permission:

Step 13 Verify that your SSH is working without an authentication or password prompt:

Caution The Fault Management service will not start if SSH prompts for authentication or a password. Be sure to complete all of the following substeps.

---

a. On node prime-ha-node1.cisco.com, enter:

b. On node prime-ha-node2.cisco.com, enter:

c. If you are prompted for a password, check the permissions of all folders and files that you modified in the preceding steps.

d. If you are prompted to continue connecting, enter yes. (The prompt should appear only the first time you use SSH to connect to the node.)

Step 14 Distribute the virtual machine:

a. Click the running virtual machine and choose Shutdown > Save.

b. On the first node, copy the virtual machine definitions file to the shared directory:

c. On the second node, copy the virtual machine definition to the second node:

Distributing the Node.tar File

Step 1 Insert the Cisco Prime Central 1.4 USB, navigate to the High Availability/RHCS Bare Metal Local HA/Fault Management folder, and locate the primefm_v1.4_ha_node.tar.gz file.

Step 2 Use SSH to connect to the first node.

Step 3 Copy the primefm_v1.4_ha_node.tar.gz file to the first node.

Step 4 Back up the /etc/cluster/ and /images directories.

Step 5 Distribute the file:

Step 6 Edit the fm_status.sh file by changing VM_FQDN to your virtual machine’s FQDN:

For example:

Distributing the Virtual Machine.tar File

Step 1 Insert the Cisco Prime Central 1.4 USB, navigate to the High Availability/RHCS Bare Metal Local HA/Fault Management folder, and locate the primefm_v1.4_ha_vm.tar.gz file.

Step 2 Mount the shared drive. (The shared storage should still be mounted to the first node. If not, verify that the shared storage is not mounted to the other node; then, mount it to the first node.)

Step 3 Launch the virtual machine:

Step 4 Use SSH to connect to the virtual machine.

Step 5 Copy the primefm_v1.4_ha_vm.tar.gz file to the virtual machine.

Step 6 Back up the /root/ha-stuff/fm and /usr/local/bin directories.

Step 7 Distribute the file:

Installing Prime Central Fault Management on the Virtual Machine

You can use the GUI to install Fault Management on the virtual machine, or you can install it silently. The following procedures explain both the GUI-based and silent installation options; choose your preferred option.

GUI-Based Installation

Step 1 Use SSH to connect to the virtual machine.

Step 2 Enter:

Step 3 Install Prime Central Fault Management:

At the installer prompts, enter the information described in the Cisco Prime Central 1.4 Quick Start Guide, section “Installing Prime Central Fault Management on the Server.”

Step 4 In another terminal window, check the installation process:

Step 5 After the installation succeeds, use SSH to connect to the Prime Central HA active server and enter:

Step 6 To test the Prime Central Fault Management installation, open a browser, log in to the Prime Central portal, and verify that the Prime Central Fault Management component is running.

Silent Installation

Step 1 Use SSH to connect to the virtual machine.

Step 2 Enter:

Step 3 Edit the fm_install.properties file to match your setup.

Step 4 Install Prime Central Fault Management:

Step 5 In another terminal window, check the installation process:

Step 6 The silent installation does not report errors. To see if any errors occurred, check the log files—starting with primefm.log—in the /opt/primeusr/faultmgmt/install/log folder.

Step 7 After the installation succeeds, use SSH to connect to the Prime Central HA active server and enter:

Step 8 To test the Prime Central Fault Management installation, open a browser, log in to the Prime Central portal, and verify that the Prime Central Fault Management component is running.

Step 9 Remove the fm_install.properties file, which contains your server’s passwords used during the silent installation.

Setting Up the Fault Management Cluster Service

Step 1 Run the 6.5 cluster workaround on both nodes (see https://access.redhat.com/knowledge/solutions/67583):

Step 2 Verify that the system contains a user named ricci. If the ricci user is missing, enter:

Step 3 On both nodes, edit and save the vm.sh agent to allow a longer start time for the Fault Management virtual machine. (If you are using different hardware, you might need to increase the timeout value.)

a. Enter:

b. Locate the timeout value (in seconds):

c. Change the timeout value to:

Step 4 Modify the /etc/cluster/cluster.conf file and set unique values. 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 Troubleshooting.

Step 5 Copy the edited cluster.conf file to the /etc/cluster/ directory on both nodes.

If the cluster is not up and running when you change the cluster.conf file, manually copy cluster.conf to the other node; then, restart the cluster:

Step 6 Validate the cluster.conf file:

Step 7 Install luci and ricci (if they are not already installed):

Step 8 Start the ricci service on both nodes:

Note Enter the passwd ricci command only once; doing so creates a password for the user ricci.

Step 9 Start the cluster services on both nodes:

Step 10 (Only if you are using the RHCS luci GUI) On the first node only, start the luci service:

Step 11 (Only if you are using the RHCS luci GUI) Log in to luci on the node where you started the luci service; for example:

Checking the Cluster Services

Step 1 Review the cluster log file in /var/log/messages.

Step 2 Check the status of the cluster:

The output is similar to the following:

Step 3 Test the Prime Central Fault Management installation:

a. Open a browser, log in to the Prime Central portal, and verify that the Prime Central Fault Management component is running.

b. Relocate the virtual machine:

c. After the relocation is complete, reverify that the Fault Management component is running on the Prime Central portal.

Step 4 After the Fault Management service is running in an HA cluster, you cannot restart its components (such as Netcool/Impact, OMNIbus, and Tivoli Common Reporting [TCR]) without first freezing the cluster. After you restart the component, you can unfreeze the cluster.

To restart a Fault Management component:

a. On the active Fault Management node, enter:

b. Use SSH to connect to the Fault Management virtual machine and enter:

c. Use SSH to connect to the active Fault Management node and enter:

Next Steps

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

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

Step 2 (On the first node only) Configure luci to start automatically upon bootup:

Step 3 Verify that the required ports are open. For a list of ports that the Fault Management component requires, see “Prime Central Protocols and Ports” in the Cisco Prime Central 1.4 Quick Start Guide.

Step 4 (On both nodes and on the virtual machine) Enable the firewall:

Step 5 Disable SELinux: