Before You Begin
1. Maintenance Pack 1 (release version 126.96.36.199) is installed on top of Cisco EPN Manager 1.2. If you have not already installed Cisco EPN Manager 1.2, install it now. Refer to the installation instructions in the Cisco Evolved Programmable Network Manager 1.2 Quick Start Guide .
2. Run the PrepForSignedUBF.sh script on the Cisco EPN Manager 1.2 server to prepare the server for installation of the Maintenance Pack 1 signed UBF.
– Download the script from the Software Download page on Cisco.com.
– A Readme file with instructions for running the script is available. Click on the Cisco EPN Manager Maintenance Pack 1 item in the Software Download page to open a Details popup. Click the Readme link at the bottom of the popup.
3. If you have Internet connectivity on the Cisco EPN Manager server, you can download and install the maintenance pack directly from the Cisco EPN Manager 1.2 GUI. If the server does not have Internet connectivity, you can download the installation file from the Software Download page on Cisco.com on another machine, copy it to the Cisco EPN Manager server and upload it through the GUI.
To download and install Cisco EPN Manager 1.2. MP1:
Step 1 Log into Cisco EPN Manager as a user with Administrator privileges.
Step 2 Open the left sidebar and choose Administration > Licenses and Software Update > Software Update.
Step 3 If your server has Internet connectivity, you can download the installation file (.ubf) directly from Cisco.com:
a. Click the blue Download link at the top of the page and log into Cisco.com. The system checks for available software updates.
b. Select Cisco EPN Manager Maintenance Pack version 188.8.131.52 and click Install.
If your server does not have Internet connectivity:
a. Download the Cisco EPN Manager 1.2. MP1 installation file (.ubf) on another machine from the Software Download page on Cisco.com.
b. Copy the.ubf file to the Cisco EPN Manager server.
c. Click the blue Upload link at the top of the page, browse to the.ubf file and click OK. When the upload is complete, the uploaded file will be listed in the Software Update page.
d. Click Install.
Step 4 In the displayed message indicating that a restart will be required, click Yes.
Step 5 Click Yes in any subsequent messages to continue with the installation.
Step 6 When the installation is complete, EPN Manager Maintenance Pack Version 184.108.40.206 will appear under Status of Updates, and the status will be Installed (Requires Restart).
Step 7 Log out and restart Cisco EPN Manager:
a. Log into the server as a Cisco EPN Manager CLI admin user.
b. Stop and restart Cisco EPN Manager.
admin# ncs stop
admin# ncs start
Installation Instructions (High Availability)
Before you Begin
1. These installation instructions assume that HA has already been configured for Cisco EPN Manager 1.2. Instructions for HA installation can be found in the Cisco Evolved Programmable Network Manager 1.2 Quick Start Guide .
- Make sure you have the password (authentication key) that was created when HA was enabled. You will need it to install the maintenance pack on the secondary server.
- Copy the installation file (.ubf) to the secondary server so that you can upload and install it.
To install Cisco EPN Manager 1.2. MP1 in a high availability environment:
Step 1 Ensure that your HA implementation is enabled and ready to be updated.
a. Log into the Cisco EPN Manager GUI on the primary server as an Admin user.
b. Select Administration > Settings > High Availability, then confirm that the primary server's state on the HA Status page is Primary Active.
c. Select HA Configuration, then confirm that the Configuration Mode is HA Enabled.
Note We recommend that you set the Failover Type to Manual during the MP installation process. If necessary, you can change that setting on the HA Configuration page.
d. Access the secondary server's Health Monitor (HM) web page by pointing your browser to the following URL:
where ServerIP is the IP address or host name of the secondary server.
e. Enter the password (authentication key), then click Login.
f. Verify that the secondary server state displayed on the HM web page is Secondary Syncing.
Step 2 Install Cisco EPN Manager 1.2. MP1 on the primary server following Steps 1 to 6 of the Installation Instructions.
Note Do not restart the primary server at this stage.
Step 3 Install Cisco EPN Manager 1.2. MP1 on the secondary server:
a. In the secondary server’s HM web page, click the Software Update link, enter the authentication key, and click Login.
b. Click Upload Update File and browse to the location where you saved the.ubf file.
c. Select the.ubf file, then click OK to upload the file.
d. On the Software Upload page, select the installation file and click Install.
e. After the installation is complete on the secondary server, verify that the Status of Updates table on the Software Update page shows Installed or Installed [Requires Restart] for the maintenance pack.
Step 4 Stop the secondary server first and then the primary server by running the ncs stop command.
Step 5 Restart the secondary server and check the secondary server processes and HA status:
a. Run the ncs start command to restart the secondary server processes.
b. Run the ncs status command and verify that all secondary server processes are up and running.
c. Run the ncs ha status command and verify that the secondary server's state is Secondary Lost Primary.
Step 6 Restart the primary server and check the primary server processes:
a. Run the ncs start command to restart the primary server processes.
b. Run the ncs status command and verify that the primary server's Health Monitor and other processes are up and running.
Once all the processes on the primary server are up and running, HA registration is automatically triggered between the secondary and primary servers (and an email is sent to the registered email addresses). This normally completes after a few minutes.
Step 7 Verify the HA status on the primary and secondary servers by running the ncs ha status command on both servers. You should see the following:
- The primary server state is Primary Active.
- The secondary server state is Secondary Syncing.