Release Notes for Crosswork Network Controller, Release 7.1.3
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.3
Cisco Crosswork Network Controller, Release 7.1.3
The Cisco Crosswork Network Controller 7.1.3 release notes include information about the issues resolved in this patch. For installation steps, see Patch installation workflow.
The recommended upgrade path to Crosswork Network Controller version 7.1.3 from version 7.1.0 or 7.1.0 → 7.1.1 → 7.1.2.
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.3.
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 |
| Devices are unreachable because static route rules have not been added |
|
| Audit dashboard logs incorrect username during session cleanup |
|
| Application pods not created during geo redundancy backup restore |
|
| Clarification of NB_OSS_UNREACHABLE alarm description |
|
| Crosswork Network Controller forwards alarms to external Kafka with extra unwanted bytes in the payload |
Table 2. Resolved issues in Crosswork Data Gateway
| Bug ID |
Description |
| Crosswork Network Controller CLI collection fails to onboard IOS-XR devices using aes256-gcm SSH cipher |
Table 3. Resolved issues in Traffic Engineering
| Bug ID |
Description |
| The API request for a specific network node does not return all expected L3 node attribute data |
|
| RSVP-TE count discrepancy in Dashboard and Tunnel 0 from Juniper devices are excluded |
|
| IPv6 router ID remains visible in Crosswork Network Controller UI after removal from device |
|
| The topology service reports incorrect link bandwidth for high-capacity links |
Table 4. Resolved issues in Zero Touch Provisioning
| Bug ID |
Description |
| Zero Touch Provisioning onboarding with duplicate IPs causes disk space exhaustion on Crosswork Network Controller |
Table 5. Resolved issues in Device Lifecycle Management
| Feature or issue |
Description |
| Deletion of NSO NED rules in primary are not synchronized to standby cluster |
|
| ASR9k transceivers not populated in the equipment table |
Table 6. Resolved issues in Element Management Functions
| Bug ID |
Description |
| System alarms from standby server not forwarded to external destinations |
Behavioral change: NSO keepalive configuration now required for stable RESTCONF integration
Before using Crosswork Network Controller 7.1.3, you must update the NSO keepalive configuration.
In earlier deployments, Crosswork Network Controller interactions with the NSO service-state-changes RESTCONF API could leave sessions hanging. Over time, these inactive sessions could consume all available NSO sessions and cause communication failures between CNC and NSO.
To prevent this issue, configure NSO keepalive settings in the ncs.conf file for all deployments, including Standalone NSO and NSO LSA. This configuration allows NSO to detect closed client connections and automatically clean up inactive sessions.
For configuration steps, refer to the Install the Cisco NSO function packs section in the Crosswork Network Controller Release 7.1.3 Patch Installation Workflow documentation.
For instructions on installing the Crosswork Network Controller 7.1.3 patch, see Crosswork Network Controller Release 7.1.3 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.1.3) 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