Cisco Cisco Prime Central 1.2 Installation Guide

Page of 38
35
   
c.
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 
d.
Install Prime Central:
cd /root/ha-stuff/pc
./PrimeCentral.sh 192.168.1.130 node's-root-password second-node-IP-address
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.
e.
In another terminal window, check the upgrade process:
tail -f /tmp/primecentral_install.log
f.
After the upgrade succeeds, start Prime Central:
# /usr/local/bin/pc.sh start
g.
Verify that Prime Central is running correctly; then, stop it:
/usr/local/bin/pc.sh stop
h.
Remove the virtual IP addresses:
ip addr del 192.168.1.130 dev eth0
i.
Unmount the shared partitions:
umount /opt/pc
When the upgrade completes, the log files are available in ~/upgrade/1.1.0.0-1.2.0.0/upgrade.log.
7  
Upgrading to Prime Central Fault Management 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 Fault Management.
To upgrade from Prime Central Fault Management 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/Fault Management folder, and locate the 
primefm_v1.2_ha_node.tar.gz file.
Step 3
Use SSH to connect to the first node.
Step 4
Copy the primefm_v1.2_ha_node.tar.gz file to the first node.
Step 5
Back up the /etc/cluster/ and /images directories.
Step 6
Distribute the file:
mount /dev/mapper/mpathcp1 /images
tar -zxf primefm_v1.2_ha_node.tar.gz -C / --owner root --no-same-owner
chmod 755 /images/*.sh
Step 7
Edit the fm_status.sh file by changing VM_FQDN to your virtual machine’s FQDN:
vi /images/fm_status.sh