Upgrade from Crosswork Network Controller 5.0 to 6.0 (Geo Redundant)
This topic explains the high level description of the tasks necessary to upgrade from Crosswork Network Controller version 5.0 to version 6.0 (geo redundant enabled).
Note |
Any day N activity will yield the system ineligible to migrate to a geo redundant solution. You will need to re-install the Crosswork cluster to enable geo redundancy. |
Step |
Action |
||
---|---|---|---|
1. Convert single instance NSO to NSO HA |
Follow the instructions in Convert Single Instance NSO to NSO HA topic.
|
||
2. Deploy SR-PCE |
Deploy SR-PCE in a Point of Presence (PoP) site closer to the Crosswork's Availability Zone. For more information, refer to the relevant install instructions in the Cisco IOS XRv 9000 Router Installation Guide.
|
||
3. Create backup of the Crosswork 5.0 cluster. |
Follow the instructions in Create Backup of the Cisco Crosswork Cluster topic. |
||
4. Shut down the Crosswork 5.0 cluster |
Shut down the Cisco Crosswork 5.0 cluster by powering down the VMs hosting each node (start with the Hybrid VMs).
|
||
4. Install the Crosswork Network Controller 6.0 cluster and applications. |
Follow the instructions in Install the Cisco Crosswork 6.0 Cluster and Applications topic. |
||
5. Perform the migration. |
Follow the instructions in Run Migration topic. |
||
6. Install the standby cluster and enable geo redundancy solution. |
Follow the instructions in Install the Standby Cluster and Enable Geo Redundancy topic. |
||
7. Upgrade Crosswork Data Gateway 5.0 to 6.0 (geo Redundant) |
Follow the instructions in Upgrade Crosswork Data Gateway 5.0 to 6.0 Geo Redundancy topic. |
||
8. Update the providers. |
Follow the instructions in Update Providers topic. |
||
9. Complete the geo enablement operation. |
Follow the instructions in Complete Geo Redundancy Enablement topic. |
Convert Single Instance NSO to NSO HA
This topic explains the procedure to convert a single instance NSO to NSO HA (High Availability). For detailed instructions, please refer to the NSO Administration Guide on HA.
Attention |
Make a backup and upgrade your NSO setup to the compatible version before executing the below steps. |
Follow the below guidelines to create a HA setup from a standalone NSO.
Procedure
Step 1 |
Determine the High Availability topology to follow: L2 or L3 |
Step 2 |
Make a backup of the original NSO system. |
Step 3 |
Clone the original NSO to a new instance. |
Step 4 |
Install the hcc package on both nodes. |
Step 5 |
Configure the high availability and hcc as per the selected network topology. |
Step 6 |
Request to enable high availability on both nodes. |
Step 7 |
Verify the changes made. |
Create Backup of the Cisco Crosswork Cluster
Creating a backup is a prerequisite when upgrading your current version of Cisco Crosswork to a new version.
Note |
We recommend that you create a backup only during a scheduled upgrade window. Users should not attempt to access Cisco Crosswork while the backup operation is running. |
Before you begin
Follow these guidelines whenever you create a backup:
-
Cisco Crosswork will back up the configuration of the system to an external server using SCP. Before you begin you need to have the following configuration in place and information about the SCP server available:
-
The hostname or IP address and the port number of a secure SCP server.
-
A preconfigured path on the SCP server where the backup will be stored.
-
User credentials with file read and write permissions to the directory.
-
The SCP server storage requirements will vary slightly but you must have at least 25 GB of storage.
-
-
Ensure that you have configured a destination SCP server to store the backup files. This configuration is a one-time activity.
-
After the backup operation is completed, navigate to the destination SCP server directory and ensure that the backup file is created. You will require this backup file in the later stages of the upgrade process.
-
Both the Cisco Crosswork cluster and the SCP server must be in the same IP environment. For example: If Cisco Crosswork is communicating over IPv6, so must the backup server.
-
Keep a record of the list of Crosswork applications you have installed in the current version of Cisco Crosswork, as you can only install those applications after migrating to the new version of Cisco Crosswork.
-
If you have onboarded a custom MIB package in the current version of Cisco Crosswork, download a copy of the package to your system. You will need to upload the package after you complete migrating to new version of Cisco Crosswork.
-
If you have modified the current version of Cisco Crosswork to include third-party device types, you must download the third-party device configuration file, and re-apply it to the new version of Cisco Crosswork. The device configuration file is located on the cluster node (at /mnt/cw_glusterfs/bricks/brick3/sys-oids.yaml) and on the pod (at /mnt/backup/sys-oids.yaml).
-
If Cisco Crosswork Optimization Engine has feature packs (Local Congestion Mitigation (LCM), Bandwidth Optimization (BWOpt), and Bandwidth on Demand (BWoD)) that are enabled, you must disable them before proceeding. You must also, if available, export the current list of interfaces managed by LCM or BWOpt (Traffic Engineering > Local Congestion Mitigation > Domain Identifier <domain_id> > Interface Thresholds > Export OR Traffic Engineering > Bandwidth Optimization > Interface Thresholds > Export icon).
Procedure
Step 1 |
Login to the Crosswork UI by navigating to https://<VIP>:30603. The VIP refers to the Management Virtual IP of the cluster. |
Step 2 |
Check and confirm that all the VMs are healthy and running in your cluster. |
Step 3 |
Configure an SCP backup server:
|
Step 4 |
Create a backup: |
Install the Cisco Crosswork 6.0 Cluster and Applications
This install the latest version of the Cisco Crosswork cluster and applications.
Important |
While the cluster installation is in progress, you must upgrade your NSO setup to the compatible version. Please monitor actively to ensure that the NSO leader is in the same site as Crosswork. |
Before you begin
-
Make sure that your environment meets all the installation prerequisites (see Installation Prerequisites for VMware vCenter).
Procedure
Step 1 |
Install Cisco Crosswork 6.0 cluster (see Install Crosswork Cluster on VMware vCenter) using the same IP addresses and same number of nodes as in old cluster. |
||
Step 2 |
After the installation is completed, log into the Cisco Crosswork UI (using https://<VIP>:30603) and check if all the nodes are up and running in the cluster. |
||
Step 3 |
Install the Cisco Crosswork applications which were installed in the old cluster. Ensure that you install the latest versions that are compatible with the 6.0 cluster. For installation instructions, please refer to the Install Crosswork Applications chapter.
|
||
Step 4 |
After the applications are successfully installed, check the health of the new Cisco Crosswork cluster.
|
Run Migration
After successfully installing the new versions of the Cisco Crosswork applications, proceed to migrate the Cisco Crosswork backup taken earlier to the new Cisco Crosswork cluster.
Before you begin
Before you begin, ensure that you have:
-
The hostname or IP address and the port number of a secure destination SCP server used in Create Backup of the Cisco Crosswork Cluster.
-
The name and path of the backup file created in Create Backup of the Cisco Crosswork Cluster.
-
User credentials with file read and write permissions to the directory.
Procedure
Step 1 |
Check and confirm that all the VMs are healthy and running in your cluster. |
Step 2 |
Configure an SCP backup server: |
Step 3 |
Migrate the previous Cisco Crosswork backup on the new Cisco Crosswork cluster: |
Step 4 |
After the data migration is successfully completed, check the health of the new Cisco Crosswork cluster.
|
Install the Standby Cluster and Enable Geo Redundancy
After completing the migration on the active cluster, install the standby cluster and enable geo redundancy.
Note |
When you are enabling geo redundancy after the 5.0 to 6.0 migration, you must set the following flag in the inventory file:
|
Procedure
Step 1 |
In the second site, install the standby cluster. For more information, refer to the installation instructions in Install Cisco Crosswork on VMware vCenter using Cluster Installer Tool or Manual Installation of Cisco Crosswork using vCenter vSphere UI. |
||
Step 2 |
Install the applications (that were installed on the active cluster) on the standby cluster.
|
||
Step 3 |
Ensure DNS connectivity on both sites. Perform DNS server update on both sites if needed to ensure that Crosswork cluster is using the right DNS server. |
||
Step 4 |
Ensure unified cross cluster endpoint is resolved on site 1 (active site). |
||
Step 5 |
Create and upload the inventory file on site 1 to create the active cluster, and verify the operation. For more information, refer to the instructions in Enable Geo Redundancy. |
Upgrade Crosswork Data Gateway 5.0 to 6.0 Geo Redundancy
This topic explains the procedure to upgrade from Crosswork Data Gateway version 5.0 to version 6.0 (geo redundant enabled).
For the 6.0 Crosswork Network Controller release, it is mandatory to deploy Crosswork Data Gateway using the FQDN. When Crosswork undergoes an upgrade, the existing data gateways transition to the ERROR state because of their enrollment using the VIP address, resulting in a discrepancy in the enrollment information.
To install Crosswork Data Gateway after an upgrade:
Before you begin
Ensure that you are aware of the following:
-
After Crosswork is upgraded, the data gateways, virtual data gateways, HA pool, and device-mapping configuration are restored.
-
The Data Gateway Manager automatically assigns the active Crosswork site as the default site for all existing data gateways.
Procedure
Step 1 |
Redeploy the Crosswork Data Gateway instance by removing the old instance and replacing it with a new installation. During the redeployment, use the unified management FQDN for ControllerIP in the OVF deployment script. For information on removing a data gateway instance, see Delete Crosswork Data Gateway from the Crosswork Cluster and installing a new instance, see Install Geo HA Crosswork Data Gateway. If the data gateways are redeployed using the same name and hostname attribute provided in the OVF script, the Data Gateway Manager considers them as existing gateways and automatically enrolls them with the upgraded Crosswork during the migration process.
|
||
Step 2 |
Modify the high availability Crosswork Data Gateway pools as following:
|
||
Step 3 |
Accept an upgrade acknowledgment message that appears on the Crosswork UI when all the data gateways with the Assigned role are in the UP state and the Spare gateways in the NOT_READY state. |
What to do next
Update Providers
After enabling geo redundancy on the active cluster, update the providers.
Note |
Skip this step if you are not planning to enable geo redundancy. |
Procedure
Step 1 |
Add the RBAC JWT token on the Cisco NSO VMs. |
||
Step 2 |
Upload and update the JWT package on the Cisco NSO High Availability VMs. |
||
Step 3 |
Reload the NCS packages on both VMs. |
||
Step 4 |
Update the JWT auth file with geo-CW FQDN cnc-host value on both VMs. |
||
Step 5 |
Update the cert.pem on both VMs. |
||
Step 6 |
Update NSO with unified cluster endpoint in the Manage Providers window. |
||
Step 7 |
(Optional) Update SR-PCE IP address in the Manage Providers window. |
||
Step 8 |
(Optional) While upgrading from a non-HA setup to geo redundant mode, Crosswork Data Gateway will end with multiple VIPs for southbound devices. These devices need to be set up for syslogs, traps and MDT. In case of MDT, you can use admin DOWN/UP to push the configuration changes to the devices.
|
Complete Geo Redundancy Enablement
After updating the providers, activate geo redundancy on the standby cluster.
Note |
Skip this step if you are not planning to enable geo redundancy. |
Procedure
Step 1 |
Create and upload the cluster inventory file on site 2, to create the standby cluster. Verify the operation. For more information, refer to the instructions in Enable Geo Redundancy. |
Step 2 |
Configure the cross cluster settings. For more information, see step 7 in the Geo Redundancy Workflow (Day 0) topic. |
Step 3 |
Perform a on-demand sync to sync the data from active to standby cluster. |