Upgrade to Cisco EPN Manager 6.1

You can upgrade to Cisco EPN Manager 6.1 by following one of the Upgrade Paths for Cisco EPN Manager 6.1.

This chapter provides instructions for upgrading to Cisco EPN Manager 6.1 using Backup-restore upgrade.


Note

Bare metal is not supported in Cisco EPN Manager 6.1. Migrate to ESXi based host before upgrading, if EPNM is not already running on virtual machine

Backup-restore upgrade consists of the following steps:

  • Backup all data from the currently installed version of Cisco EPN Manager.

  • Install Cisco EPN Manager 6.0 OVA (if current version is running on bera metal, you need to migrate to an ESXi based host first).

  • Restore backup on the new Cisco EPN Manager 6.0.

  • Install Cisco EPN Manager 6.1 UBF.

Upgrade Paths for Cisco EPN Manager 6.1

The following table lists the valid paths for upgrading to Cisco EPN Manager 6.1 from previous versions.

Current Cisco EPN Manager Version

Installation Path to Cisco EPN Manager 6.1.0

Cisco EPN Manager 6.0.0

Cisco EPN Manager 6.0.1

Cisco EPN Manager 6.0.0 (restore) > 6.0.1 > 6.1.0

Cisco EPN Manager 6.0.2

Cisco EPN Manager 6.0.0 (restore) > 6.0.2 > 6.1.0

Cisco EPN Manager 5.1.4.1

Cisco EPN Manager 5.1.4.1 > 6.0.0 (restore) > 6.0.1 > 6.1.0

See the relevant installation guide for installation prerequisites and procedures for Cisco EPN Manager versions.

For point patch installation instructions, see the readme file supplied with the patch file on the Software Download site on Cisco.com.

Upgrade to Cisco EPN Manager 6.1 (No HA)

These topics explain how to upgrade to Cisco EPN Manager 6.1 from an earlier version of Cisco EPN Manager in a standard deployment (no high availability).

If you are performing an upgrade in a high availability deployment, see Upgrade to Cisco EPN Manager 6.1 (High Availability).

Backup-Restore Upgrade (No HA)

Backup-restore upgrade involves backing up all data from the currently installed version of Cisco EPN Manager, then installing Cisco EPN Manager 6.1 on a new server, then restoring the backed up data to the new Cisco EPN Manager 6.1 server. This is the recommended upgrade method.

Before You Begin

  • Make sure the new server has the same hardware specifications as the server from which the backup was taken.

  • Note the location of the remote backup repository used by the old server. You will need it to configure the same backup location on the new server.

Procedure

Step 1

Configure the new server to use the same remote backup repository as the old server, as explained in the remote backup repository topics in the Cisco Evolved Programmable Network Manager User and Administrator Guide .

Step 2

Restore the backup in the remote repository to the new server, as explained in the restore backup topics in the Cisco Evolved Programmable Network Manager User and Administrator Guide .

Upgrade to Cisco EPN Manager 6.1 (High Availability)

The following topic provides the procedure for upgrading to Cisco EPN Manager 6.1 in a high availability deployment:

Backup-Restore Upgrade (High Availability)


Note
High availability will not be functional until the upgrade is complete.

Backup-Restore Upgrade (High Availability)

Backup-restore upgrade in an HA environment involves the following basic steps which are explained in detail in the procedure below:

  1. Back up your data to a remote repository.

  2. Perform a fresh installation of Cisco EPN Manager on both the primary and secondary servers.

  3. Restore the backup data on the primary server.

  4. Reconfigure HA.

Before You Begin

  • Make sure your deployment meets the general HA requirements.

  • Make sure your deployment meets the upgrade-specific requirements.

  • Make sure the new server has at least the same hardware specifications as the server from which the backup was taken.

  • 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.

  • Make sure that you have the password (authentication key) that was created when HA was enabled. You will need it to perform the Cisco EPN Manager 6.1 installation on the secondary server.

Procedure

Step 1

On the primary server, remove the High Availability configuration:

  1. Log into Cisco EPN Manager as a user with Administrator privileges.

  2. Choose Administration > Settings > High Availability.

  3. Make a note of the HA configuration. You will need this information to reconfigure HA after the upgrade.

  4. Choose HA Configuration in the left navigation area, then click Remove.

  5. Wait for the remove operation to complete.

  6. Click HA Configuration in the left navigation area and confirm that the Configuration Mode field displays HA Not Configured.

Step 2

Backup your data to the remote repository. For details, see the topics on backups in the Cisco Evolved Programmable Network Manager User and Administrator Guide.

Note 
If you do not have a remote repository, configure one. See the topics on remote backup repositories in the Cisco Evolved Programmable Network Manager User and Administrator Guide.
Step 3

Configure the new primary server to use the same remote backup repository as the old primary server (which you used in Step 2). See the topics on remote backup repositories in the Cisco Evolved Programmable Network Manager User and Administrator Guide.

Step 4

On the primary server (only), restore the backup from the remote repository. See the topics on restoring data in the Cisco Evolved Programmable Network Manager User and Administrator Guide .

Note 
You only need to perform the restore operation on the primary server. The secondary server will be synchronized with the primary server when HA is re-enabled.
Step 5

On the primary server:

  1. Verify that the server is restarted.

  2. Run the ncs status command and make sure that the Health Monitor process and other processes have restarted. Ensure that, at a minimum, the following services are up and running: Health Monitor, Database, NMS, SAM Daemon, DA Daemon. Note that for optimal Cisco EPN Manager functionality, all services should be up and running.

Step 6

If the ncs status output on the primary server lists Compliance engine is stopped, do the following:

  1. Stop Cisco EPN Manager. 

    
ncs stop

  2. Log in as the Linux CLI root user.

  3. 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 7

Once the restore is completed, perform the post-upgrade tasks on the primary server. See Post-Upgrade Tasks.

Step 8

Re-configure HA by registering the secondary server on the primary server. Use the information you saved in Step 1. 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 Cisco Evolved Programmable Network Manager User and Administrator Guide.

Post-Upgrade Tasks

  • 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 Cisco Evolved Programmable Network Manager User and Administrator Guide .

  • Synchronize the inventory of all devices with the database, as follows:

    1. In the Cisco EPN Manager GUI, choose Monitor > Network Devices.

    2. Select all devices, then click Sync.

  • Instruct users 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.

  • If you were using external AAA before the upgrade, configure external authentication again. Refer to the user management topics in the Cisco Evolved Programmable Network Manager User and Administrator Guide.

  • During the upgrade, the Cisco EPN Manager home page will be reset to the default home page (Getting Started page). Users can select their own default home page from the Getting Started page or from the Settings menu at the top right of the page.

New dashlets on existing tabs, will not be added automatically post upgrade. The user can manually add them from the dashboard menu Settings->Add Dashlet(s).

New dashboard tabs will be added automatically.