The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
![]() Note | In a high availability environment, the point patch and MP1 must be installed on both the primary and secondary servers. |
These are the steps for installing Cisco EPN Manager 2.0 MP1 in a deployment configured with high availability:
Installing PP2 (Cisco EPN Manager 2.0 (0.2.0)) is mandatory for MP1 installation and PP2 includes the contents of PP1 (Cisco EPN Manager 2.0 (0.1.0)) as well. Therefore, if you have not yet installed PP1, you can directly proceed to PP2 installation.
Follow these steps to install a point patch on top of Cisco EPN Manager 2.0 in a deployment that is already configured for high availability, where the secondary server is registered to a primary server. The point patch must be installed on both the primary and secondary servers.
![]() Note | You must start the patch install with the primary server in the Primary Active state and the secondary server in Secondary Syncing state. See the installation steps below for details. |
Patching of primary and secondary HA servers takes approximately one hour. During that period, both servers will be down.
Step 1 | Check the HA status on the primary server: |
Step 2 | Check the HA
status on the secondary server:
|
Step 3 | On the secondary
server, download and install the patch:
|
Step 4 | On the primary server, download and install the patch. Follow Steps 1 to 5 in Download and Install the Point Patch (No HA). |
Step 5 | The primary server restarts automatically and the GUI will not be accessible for sometime. |
Step 6 | On the primary server, run the following commands in a CLI session: |
Step 7 | Verify that the patch is listed as "Installed" in the Software Update page of the primary server. |
Step 8 | Check if the version of the Point Patch is listed correctly in the Login, About and Software Update pages in the Cisco EPN Manager GUI. |
IMPORTANT : The following procedure is only required if you are installing Cisco EPN Manager 2.0 MP1 after upgrading from Cisco EPN Manager 1.2 MP7.
If you are upgrading from Cisco EPN Manager 1.2 MP7, you must run a mandatory script that performs some required configurations to the optimizer. The following procedure explains how to download the script and signature files, validate the script image, and run the script.
![]() Note | This script must be run only on the primary server after removing the HA configuration. |
Step 1 | On the primary server, remove the HA configuration. |
Step 2 | Download and run the script by following the instructions in Download and Run the EpnmMP1_prereq_sys_stats Script (No HA). |
Step 1 | Back up your
data by performing a manual application backup (or, for virtual machines, by
taking a snapshot of the virtual machine (VM)). If the primary server goes down
when you install the MP, you can use this backup to restore your data.
The following steps explain how to perform an application backup using the web GUI.
| ||
Step 2 | On the primary server, upload/download the Cisco EPN Manager 2.0. MP1 ubf file. Follow Steps 1 to 3 in Download Cisco EPN Manager 2.0. MP1 (No HA). | ||
Step 3 | Upload the
Cisco EPN
Manager 2.0. MP1 ubf file to the secondary server:
|
After the download/upload of the MP1, proceed with its installation.
If you are upgrading from Cisco EPN Manager 1.2 MP7, first run the prerequisite script as detailed in Download and Run the EpnmMP1_prereq_sys_stats Script (HA Deployment) and proceed from Step 2 in the below listed steps for installing the Maintenance Pack.