Cisco Cisco Evolved Programmable Network Manager 2.0 Installation Guide
33
Step 16
On the primary server:
a.
Verify that the server is restarted.
b.
Run the ncs status command and make sure that the Health Monitor process and other processes have restarted.
Step 17
If the ncs status output on the primary server lists Compliance engine is stopped, do the following:
a.
Stop Cisco EPN Manager.
ncs stop
b.
Log in as the Linux CLI root user (see
. Be sure to use the procedures for Cisco EPN Manager 2.x.
c.
Update the time zone using a soft link (the following command is one line):
ln -sf /usr/share/zoneinfo/$(grep ^clock /storedconfig/active/startup-config | cut
-d " " -f 3) /etc/localtime
Step 18
On the secondary server:
a.
Verify that the server is restarted.
b.
Run the ncs status command and make sure that the Health Monitor process and other processes have restarted.
Step 19
Perform the following post-upgrade tasks on the primary server:
•
If you are using Cisco Smart Licensing, re-register Cisco EPN Manager with the Cisco Smart Software Manager
(CSSM) on Cisco.com. Refer to the topics that describe managing licenses in the
(CSSM) on Cisco.com. Refer to the topics that describe managing licenses in the
•
Instruct user to clear the browser cache on all client machines that accessed an older version of Cisco EPN Manager
before they try to connect to the upgraded Cisco EPN Manager server.
before they try to connect to the upgraded Cisco EPN Manager server.
•
If you were using external AAA before the upgrade, configure external authentication by referring to the user
management topics in the
management topics in the
.
Step 20
Once the post upgrade tasks are completed, re-configure HA by registering the secondary server on the primary server.
Use the information you saved in
Use the information you saved in
. The registration process must be performed from the primary server. For more
information, see the section on registering the secondary server on the primary server, in the
Perform a Backup-Restore Upgrade (High Availability)
For an HA backup-restore upgrade, you will perform the following steps:
1.
Remove HA.
2.
Back up your data to a remote repository.
3.
Perform a fresh installation of CEPNM on both the primary and secondary servers.
4.
Restore the backup data on the primary server.
5.
Reconfigure HA.
Before You Begin
•
Make sure your deployment meets the general HA requirements listed in
.
•
Make sure your deployment meets the upgrade-specific requirements listed in
.
•
Note the location of the remote backup repository used by the old server (if applicable). You will need it to configure the
same backup location on the new server.
same backup location on the new server.