Release Notes for Crosswork Network Controller, Release 7.1.2
Available Languages
Bias-Free Language
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.
- US/Canada 800-553-2447
- Worldwide Support Phone Numbers
- All Tools
Feedback
Feedback
Cisco Crosswork Network Controller, Release 7.1.2
Cisco Crosswork Network Controller, Release 7.1.2
The Cisco Crosswork Network Controller 7.1.2 release notes list the resolved issues included in this patch and provide instructions for installing it. For installation steps, see Patch installation workflow.
The recommended upgrade path to Crosswork Network Controller version 7.1.2 from version 7.1.1 or 7.1.0. If you have additional questions not addressed in this document, contact Cisco Customer Experience.
There are no new software features in this release.
The tables below outline the resolved issues in Crosswork Network Controller version 7.1.2.
This software release may include bug fixes that were introduced in previous versions. For more details, click the bug ID to access the Cisco Bug Search Tool.
Refer to the Cisco bug search tool section below for instructions on how to use the tool.
Table 1. Resolved issues in Platform Infrastructure
| Bug ID |
Description |
| Accessing Manage Provisioning NSO fails on Crosswork Network Controller UI after migration to a different IP address. |
|
| Certificate renewal fails in IPv6 and dual-stack deployments because the renewal script cannot parse IPv6 addresses. |
|
| When robot-orch restarts after a failed patch upgrade, it incorrectly attempts to upgrade the already-installed patch version instead of retrying the failed upgrade. |
|
| Crosswork Network Controller fails to send notifications for coherent and optics interfaces during fiber cut events. |
Table 2. Resolved issues in Crosswork Data Gateway
| Bug ID |
Description |
| The ifPhysAddress field is returned as a UTF-8–encoded string instead of the expected hexadecimal format, which prevents proper parsing and processing of the physical address. |
Table 3. Resolved issues in Traffic Engineering
| Bug ID |
Description |
| Link Aggregation Group (LAG) incorrectly shows "degraded" instead of "down" in Crosswork topology when Bundle-Ether interface is shutdown. |
|
| Auto-onboarding from SR-PCE topology fails during GEO-HA sync when pods enter maintenance mode, preventing device addition during synchronization. |
|
| The RSVP API parser reports errors for valid Juniper configurations that use tunnel ID 0 or loopback0.0 interfaces. |
|
| Devices may appear isolated with missing or degraded links after changing the network domain identifier. |
|
| Path calculation server connection may not disconnect properly after removing the provider from settings. |
|
| SR-PCE process crash is observed when path response from Bandwidth on Demand COE function pack exceeds 64KB. |
|
| PrefixSID is not removed due to [attrFlag: 96] parsing issue in topology service. |
Table 4. Resolved issues in Change Automation and Health Insights
| Bug ID |
Description |
| KPI Profile page does not display already created profiles when worker node is shutdown. |
|
| Change Automation play fails with an InternalFailure error. |
Table 5. Resolved issues in Device Lifecycle Management
| Feature or issue |
Description |
| Crosswork Network Controller fails to properly connect Bundle interfaces with their member physical ports during device discovery. |
|
| Config download API fails when attribute values contain colon (':') characters in request headers. |
|
| The trap generated for the Device Unreachable alarm does not include the hostname or IP address in the cenUserMessage1 field. |
Table 6. Resolved issues in Element Management Functions
| Bug ID |
Description |
| Device-config service retry mechanism is not able to recover the service while processing a Geo notification. |
Important notes
Consider the following important information before using Crosswork Network Controller 7.1.2:
NSO keepalive configuration required for stable RESTCONF integration
Previous CNC interactions with NSO's service-state-changes RESTCONF API caused "hanging" sessions that exhausted NSO's session limits, rendering it unresponsive. To prevent this and ensure stable RESTCONF integration, configure NSO keepalive settings in the ncs.conf file for all deployments, including Standalone NSO and NSO LSA. This configuration enables NSO to detect closed client connections and clean up inactive sessions. For details on configuring these settings, refer to the Install the Cisco NSO function packs section in the Crosswork Network Controller Release 7.1.2 Patch Installation Workflow documentation.
For instructions on installing the Crosswork Network Controller 7.1.2 patch, see Crosswork Network Controller Release 7.1.2 Patch Installation Workflow.
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 drop-down list, select Series/Model and enter Cloud and Systems Management in the search field.
4. Click Select from List and select Cloud and Systems Management > Routing and Switching Management > Cisco Crosswork Network Automation.
5. From the Release drop-down list, choose the appropriate filter as, Affecting or Fixed in Releases, Affecting Releases, or Fixed in Releases and enter the release version (for example, 7.0.5) in the search field.
6. (Optional) You can enter additional criteria (such as bug ID, problem description, a feature, or a product name) in the search field.
7. 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.
8. To export the results to a spreadsheet, click Export Results to Excel.
Accessibility features
For a list of accessibility features in Cisco Crosswork Network Controller, visit VPAT Documents or contact accessibility@cisco.com.
All product documents except for some images, graphics, and charts are accessible. If you would like to receive the product documentation in audio format, braille, or large print, contact accessibility@cisco.com.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2026 Cisco Systems, Inc. All rights reserved