First Published: March 28, 2025

The Cisco Crosswork Network Controller 7.0.2 release includes new functionality, minor enhancements, and important bug fixes. This document describes what’s new, the resolved bugs, and how to install the patch.

If you have additional questions not addressed in this document, contact Cisco Customer Experience.

What's new in this release

This table lists the primary new features and functionality introduced in Crosswork Network Controller 7.0.2:

Table 1. New features in Crosswork Network Controller 7.0.2

Category

What's new

Support for SR-TE path validation through Optimization Engine integration

Two new plays are available to automate the verification of SR-TE paths against the network's Label Switch Path (LSP). By using these plays together, you can ensure that the paths meet optimal performance and reliability standards.

  • Get Head-End TE-Router-ID play: Retrieves the head-end TE-Router-ID of the SR-TE path, enabling precise path identification and validation.

  • Request SR Policy from Optimization Engine play: Collects the SR policy hop details using Optimization Engine API. This play verifies the SR-TE hop list against the network model's specific criteria, such as bandwidth availability, minimal delay, and efficient resource utilization.

Third-party device support

Support of configured IP addresses on interfaces for generic third-party devices. This feature allows Element Management Functions to collect and populate IP addresses for interfaces into its database, improving device management and network visibility.

Device support

Support added for IOS-XR Device (Cisco NCS 55A1-24Q6H-SS).

Resolved bugs

The Crosswork Network Controller 7.0.2 patch resolves these Crosswork Network Controller bugs:

See the Find additional details section on how to use the Cisco Bug Search Tool to get more information on these bugs.

Table 2. Platform Infrastructure

Bug ID

Bug description

CSCwk88190

After scrolling down through a collection job, if the list of tasks exceeds 100 jobs, the Tasks (RHS) information is cut off

CSCwn15848

Crosswork Network Services Orchestrator function pack deployer fails with sshd_config MaxSessions=1 on Crosswork Network Services Orchestrator server

CSCwn20844

A Tyk restart issue occurs during the certificate upload

CSCwn48318

Failure to update external Kafka mutual authentication certificates

CSCwn64373

After a VM reboot, a lag occurs in local-postgres

CSCwn75723

The smart licensing error, "Communication send error", displays when trying to authenticate with HTTPS

CSCwn88424

The standby GEO cluster returns status 100 for GET request on port 30652
Table 3. Element Management Functions

Bug ID

Bug description

CSCwn50624

Element Management Functions TP API Query missing response for PE-CE Link (Virtual UNI) information

CSCwn61457

A delay in LAG discovery between Crosswork Network Controller and TP API correlation occurs

CSCwn63879

Inconsistency identified in TPs API call response and Crosswork Network Controller UI

CSCwn77303

Small Form-factor Pluggables (SFPs) are not appearing for the ASR9K
Table 4. Optimization Engine

Bug ID

Bug description

CSCwm84132

Optima-engine & optima-ui services show as healthy even though neither are working as expected

CSCwn26875

Juniper SR policy traffic reported using active LSP path name

CSCwn58574

Local Congestion Mitigation (LCM) misclassifies a detour policy
Table 5. Active Topology

Bug ID

Bug description

CSCwm13217

Error: cat-service-overlay degraded with NATS connection error

CSCwn76895

The Active Topology function pack is not working properly when service YANG has enumerations with space characters
Table 6. Service Health

Bug ID

Bug description

CSCwm46461

Check Helios response to determine template job operation status

CSCwn64309

Heuristic package customization with GNMI Sensor returns Unsupported Type

CSCwn87025

Heuristic package customization requires logging support for Python plugin
Table 7. Topology

Bug ID

Bug description

CSCwm77267

Unable to install offline geo maps in an airgapped installation

CSCwn12425

Device alarms icon in map not updating with 1000 alarms

CSCwn98069

Duplicate L2 LAG links found in the Crosswork Network Controller UI

Find additional bug details

You can use the Cisco Bug Search Tool to see additional details for selected bug IDs listed in the Crosswork Network Controller 7.0.2 component tables.

  1. Go to the Cisco Bug Search Tool.

  2. Enter your registered Cisco.com username and password, and click Log In.

    The Bug Search page opens.


    Note

    If you do not have a Cisco.com username and password, you can register here.

  3. From the Product list, select Cloud and Systems Management > Routing and Switching Management > Cisco Crosswork Network Automation.

  4. Enter 7.0.2 in the Release field.

  5. (Optional) You can enter additional criteria (such as bug ID, problem description, a feature, or a product name) in the Search For field.

  6. Click Search. When the search results are displayed, use the filter tools to narrow the results. You can filter the bugs by status, severity, and so on.


Note

To export the results to a spreadsheet, click Export Results to Excel.

Patch installation workflow

This section provides the high-level workflow for installing the Crosswork Network Controller 7.0.2 patch.

Table 8. Patch installation workflow

Step

Action

1. Ensure that your environment meets all the installation prerequisites.

Refer to the guidelines in Patch installation prerequisites.

2. Compare the versions of your current Crosswork applications with the new patch versions to determine which applications need an upgrade. Download only the upgrades for the versions you need.

See Download Cisco Crosswork Network Controller 7.0.2 component patch files for more information.

3. Extract and validate the Crosswork Network Controller 7.0.2 patch files.

Refer to the guidelines in Extract and validate 7.0.2 patch files.

4. Copy and execute the Crosswork Infrastructure MOP script.

Refer to the guidelines in Copy and execute the Crosswork Infrastructure MOP.

5. Take a back up of both your data and the NSO data.

See Back up your data for more information.

6. Add and install the 7.0.2 patch files in the Crosswork Network Controller UI.

Refer to the guidelines in Add and install 7.0.2 patch files.

(Optional) 7. Add and install the Geo Redundancy patch.

Note

 

The installation of this patch is only required if geo redundancy is in use. If you are not using geo redundancy, there is no need to install this patch.

Refer to the guidelines in Install Geo Redundancy 7.0.2 patch.


Caution

The upgrade process is disruptive and should be performed during a maintenance window. The time required for the applications to restart is typically less than 30 minutes per application. If you encounter any error while installing the patch, contact the Cisco Customer Experience team before attempting to move forward with the next step.

Patch installation prerequisites

This section describes the installation prerequisites needed to install the Crosswork Network Controller 7.0.2 patch.

  • Ensure that the target system has Crosswork Network Controller version 7.0.0 installed, as well as the 7.0.0 version of any relevant components, before applying the patch upgrade. For more information, see the instructions in Cisco Crosswork Network Controller 7.0 Installation Guide.

    • Ensure that you have installed Data Gateway using the signed-cw-na-dg-7.0.0-26-release-20240918.uefi.ova file. If you are using a different version of Data Gateway, upgrade to the latest version using the files available on Cisco Software Download. For detailed instructions on how to upgrade, see Upgrade Crosswork Data Gateway.

  • Ensure that you have your Cisco Crosswork Administrator user credentials.

  • Ensure that you have the Management IP address used for your Crosswork Network Controller VM deployment.

  • Ensure that your local machine, where the patch files are downloaded, is accessible via scp by the Crosswork Network Controller.

  • In a geo redundant setup, ensure that all relevant files, such as the Crosswork Network Controller cluster, application CAPPs, and data gateways, are installed on both the active and standby clusters. Perform an on-demand synchronization operation before starting the patch installation process. Wait to perform any further syncs until the MOP and infrastructure upgrades are completed, and the services are working well.

Download Cisco Crosswork Network Controller 7.0.2 component patch files

This section provides the overview and installation sequence of all the component patch files available in the Crosswork Network Controller 7.0.2 release. Please note that some patch files may be optional for your specific needs.

Review the lists and download all the required patch files from the Cisco Software Download page to a local machine.

Multi-VM cluster deployment files

If you have deployed Crosswork Network Controller version 7.0.0 on a multi-VM cluster, and intend to install the 7.0.2 patch, you must install these files in this sequence:

  1. (Mandatory) Crosswork Infrastructure MOP file: signed-cw-na-infra-7.0.2-MOP-250203.tar.gz

  2. (Mandatory) Crosswork Infrastructure patch: signed-cw-na-infra-patch-7.0.2-11-release-250301.tar.gz

  3. (Mandatory) Element Management Functions: signed-cw-na-element-management-functions-patch-7.0.2-23-releaseems702-250303.tar.gz

  4. Crosswork Optimization Engine: signed-cw-na-coe-patch-7.0.2-5-release-250318.tar.gz

  5. Crosswork Active Topology: signed-cw-na-cat-patch-7.0.2-4-release-250312.tar.gz

  6. Crosswork Service Health: signed-cw-na-aa-patch-7.0.2-2-release-250131.tar.gz

  7. Crosswork Change Automation: signed-cw-na-ca-patch-7.0.2-5-release-250306.tar.gz

  8. Crosswork Health Insights: signed-cw-na-hi-patch-7.0.2-2-release-250213.tar.gz

  9. Geo Redundancy patch: signed-cw-na-geo-patch-7.0.2-2-release-250305.tar.gz

Single VM deployment files

If you have deployed Crosswork Network Controller version 7.0.0 on a single VM and intend to install the 7.0.2 patch, you must install these files in this sequence:

  1. Crosswork Infrastructure MOP file: signed-cw-na-infra-7.0.2-MOP-250203.tar.gz

  2. Crosswork Infrastructure patch: signed-cw-na-infra-patch-7.0.2-11-release-250301.tar.gz

  3. Embedded Collectors: signed-cw-na-dgcollectors-patch-7.0.1-19-release-241118.tar.gz

  4. Element Management Functions: signed-cw-na-element-management-functions-patch-7.0.2-23-releaseems702-250303.tar.gz

Extract and validate 7.0.2 patch files

This section explains how to extract and validate the downloaded 7.0.2 patch files. Repeat these steps for each patch file you plan to install.


Attention

It is crucial that you extract the .tar.gz file from the signed file. You must add and install this specific file through the Crosswork Network Controller UI.

Procedure

Step 1

After downloading the patch file, navigate to the folder where the tar file was downloaded. As an example, consider the Crosswork Infrastructure signed patch image (signed-cw-na-infra-patch-7.0.2-11-release-250301.tar.gz) for this procedure.

cd <folder where the tar file was downloaded>

Step 2

Extract the file using this command.

tar -xzvf <signed image file>

The file unpacks into the patch and the necessary tools to validate its contents.

Example: 
tar -xzvf signed-cw-na-infra-patch-7.0.2-11-release-250301.tar.gz
Output:
README
cw-na-infra-patch-7.0.2-11-release-250301.tar.gz
cw-na-infra-patch-7.0.2-11-release-250301.tar.gz.signature
CW-CCO_RELEASE.cer
cisco_x509_verify_release.py3

Step 3

Validate the extracted patch file using this command.

python3 cisco_x509_verify_release.py3 -e <.cer file> -i <.tar.gz file> -s <.tar.gz.signature file> -v dgst -sha512

Important

 

You must include this command as a single line, and the tool will wrap it according to the screen width.
Example:
python3 cisco_x509_verify_release.py3 -e CW-CCO_RELEASE.cer -i cw-na-infra-patch-7.0.2-11-release-250301.tar.gz -s cw-na-infra-patch-7.0.2-11-release-250301.tar.gz.signature  -v dgst -sha512
Output: 
Retrieving CA certificate from http://www.cisco.com/security/pki/certs/crcam2.cer ...
Successfully retrieved and verified crcam2.cer.
Retrieving SubCA certificate from http://www.cisco.com/security/pki/certs/innerspace.cer ...
Successfully retrieved and verified innerspace.cer.
Successfully verified root, subca and end-entity certificate chain.
Successfully fetched a public key from CW-CCO_RELEASE.cer.
Successfully verified the signature of cw-na-infra-patch-7.0.2-11-release-250301.tar.gz using CW-CCO_RELEASE.cer

Copy and execute the Crosswork Infrastructure MOP

This section explains how to copy and execute the Crosswork Infrastructure 7.0.2 MOP file.

Before you begin

Ensure you have extracted and validated the Crosswork Infrastructure MOP, cw-na-infra-7.0.2-MOP-250203.tar.gz, using the instructions in Extract and validate 7.0.2 patch files.

Procedure

Step 1

Copy the extracted MOP file using the VIP address to the /home/cw-admin/ folder on one of the Crosswork Network Controller hybrid nodes.

scp {MOP file} cw-admin@{Crosswork VIP Address}:/home/cw-admin/

Example:
scp cw-na-infra-7.0.2-MOP-250203.tar.gz cw-admin@10.10.10.10:/cw-admin/home/

Step 2

SSH into the Crosswork Network Controller hybrid node where you copied the files, and change to root using sudo su - command.

Step 3

Extract the MOP file:

tar -xzvf <MOP file>

Example:

cd /home/cw-admin
tar -xzvf cw-na-infra-7.0.2-MOP-250203.tar.gz

Output:

signed-cw-na-k8s-orchestrator-7.0.2-3-release-250203.tar.gz
update_orch.sh

Step 4

Update the permissions.

chmod 755 update_orch.sh

Step 5

Run the script file.

./update_orch.sh

When you run the script you will be asked for the password for the cw-admin user account.

Note

 

Do not enter the password more than once even if you are prompted repeatedly to do so. The script will reuse the password that it read from the earlier input.

Wait 10 to 15 minutes for the update to complete and verify that system is healthy.

Back up your data

Take a backup of both your data and the NSO data (for more information, see Manage Crosswork Network Controller Backup and Restore).

Additionally, ensure that the server being patched has sufficient space to unarchive and copy the MOP scripts. Make sure to clean up at least 5GB of space in the /home/cw-admin/ directory and 1GB of space in the /tmp/ directory to prevent any space constraints during script execution.

Add and install 7.0.2 patch files

This section explains how to add and install the 7.0.2 patch files in the Crosswork Network Controller UI.


Important

A patch upgrade is only supported if the component's 7.0.0 version is already installed on the target system.

Before you begin

Ensure you have extracted and validated the required 7.0.2 patch files using the instructions in Extract and validate 7.0.2 patch files.

Procedure

Step 1

Click on Administration > Crosswork Management, and select the Application Management tab. The Platform Infrastructure and any applications that are added are displayed here as tiles.

Step 2

Click on the Add File (.tar.gz) option to add the patch file that you extracted. As an example, consider the Platform Infrastructure patch file, cw-na-infra-patch-7.0.2-11-release-250301.tar.gz for this procedure.

Attention

 

It is crucial that you extract the .tar.gz file from the signed file. You must add and install this specific file through the Crosswork Network Controller UI.

The Add File (tar.gz) via Secure Copy popup window is displayed.

Step 3

Enter the relevant information and click Add.

Step 4

Once the patch file is added, you can observe the existing application tile displaying an upgrade prompt. Click the upgrade prompt to install the patch file.

In the Upgrade pop-up screen, select the new version that you want to upgrade to, and click Upgrade. Click on Job History to see the progress of the upgrade operation.

Step 5

After the installation is complete, go to Administration > Crosswork Manager and confirm all of the applications are reporting a Healthy status.

Note

 

It is expected that some processes will be reported as unhealthy or degraded as the upgrade is deployed (an updated status may take up to 30 minutes before reporting). If, after 30 minutes, the status does not change to Healthy, contact your Cisco Customer Experience representative. It is recommended to wait until the system is back to Healthy status before proceeding to install the next patch file.

Step 6

Repeat steps 1 to 5 to add and install the remaining Crosswork Network Controller application patch files that you need.

Install Geo Redundancy 7.0.2 patch

This section explains how to add and install the Geo Redundancy 7.0.2 patch files in the Crosswork Network Controller UI. The Geo Redundancy patch must be installed on both the active and standby clusters.


Important

The installation of this patch is only required if geo redundancy is in use. If you are not using geo redundancy, there is no need to install this patch.

Before you begin

Ensure you have extracted and validated the Geo Redundancy 7.0.2 patch, signed-cw-na-geo-patch-7.0.2-2-release-250305.tar.gz, using the instructions in Extract and validate 7.0.2 patch files.

Procedure

Step 1

On the active cluster, click on Administration > Crosswork Management, and select the Application Management tab.

Step 2

Click on the Add File (.tar.gz) option to add the patch file. The Add File (tar.gz) via Secure Copy popup window is displayed.

Attention

 

It is crucial that you extract the .tar.gz file from the signed file. You must add and install this specific file through the Crosswork Network Controller UI.

Step 3

Enter the relevant information and click Add.

Step 4

Once the patch file is added, you can observe the existing application tile displaying an upgrade prompt. Click the upgrade prompt to install the patch file.

In the Upgrade pop-up screen, select the new version that you want to upgrade to, and click Upgrade. Click on Job History to see the progress of the upgrade operation.

Step 5

After the installation is complete, go to Administration > Crosswork Manager and confirm all of the applications are reporting a Healthy status.

Step 6

Log in to the standby cluster and repeat steps 1 to 5.