Cisco Cisco Prime Central 1.2 Installation Guide

Page of 38
34
   
clusvcadm -U
 service-name
Problem
After adding multipath, you cannot see the multipath names when listing the /dev/mapper directory.
Solution
Do the following:
1.
Enter:
vi /etc/multipath.conf
2.
Change the find_multipaths value to no.
3.
Enter:
wq
service multipathd reload
You should now see the multipath names.
Problem
You receive the following error while mounting the storage:
[root@prime-central-linux4 ~]# mount /dev/mapper/mpathbp2 /images/
mount: wrong fs type, bad option, bad superblock on /dev/mapper/mpathbp2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
Solution
Enter:
fsck.ext3
 <storage-path>
fsck.ext3 /dev/mapper/mpathbp2
Problem
The fmctl status command shows that Fault Management started in KVM, but hangs in “starting” status in the cluster.
Solution
Check the SSH password-less connection between the two nodes and KVM.
6  
Upgrading to Prime Central 1.2 in a Local Redundancy HA Configuration
You must upgrade the server with Red Hat Enterprise Linux 5.5 to 5.8 before upgrading Prime Central.
To upgrade from Prime Central 1.1 to 1.2 in a local redundancy HA configuration:
Step 1
Shut down the cluster.
Step 2
Insert the Cisco Prime Central 1.2 USB, navigate to the High Availability/Prime Central folder, and locate the 
primecentral_v1.2_ha_vm.tar.gz file.
Step 3
Use SSH to connect to the first node.
Step 4
Copy the primecentral_v1.2_ha_vm.tar.gz file to the first node.
Step 5
Back up the following directories on both nodes:
/root/ha-stuff/pc
/usr/local/bin
Step 6
Distribute the file:
tar -zxf primecentral_v1.2_ha_vm.tar.gz -C / --owner root --no-same-owner
chmod 755 /root/ha-stuff/pc/*
chmod 755 /usr/local/bin/*
Step 7
On the first node only, do the following:
a.
Mount the shared partitions:
mount /dev/mapper/mpath2p1 /opt/pc
b.
Add a virtual IP cluster service address for the Prime Central service:
ip addr add 192.168.1.130 dev eth0