Release Notes for Crosswork Network Controller, Release 7.1.1

Software reliability

Support for XRv 9000 on RHEL KVM 9.x with XR 25.3.1

Crosswork Network Controller now supports SR-PCE with Cisco IOS XRv 9000, running version XR 25.3.1, deployed on the RHEL KVM 9.4 platform.

Ease of use

Network topology insights to view Link Aggregation Group (LAG) data

LAG Discovery: Link Aggregation Group (LAG) discovery now provides out-of-the-box support for third-party devices that meet the IEEE 802.3ad Link Aggregation MIB standard, which is based on the Link Aggregation Control Protocol (LACP). For devices that do not comply with this standard, contact your Cisco account representative to discuss options for custom MIB normalization.

LAG RESTCONF API: The existing topology RESTCONF API has been enhanced to provide comprehensive reporting of discovered LAG link information. Previously, discovered LAG links were not exposed through the API. With this update, the API now leverages IETF YANG models, specifically RFC 8345 for network topologies and RFC 8944 for Layer 2 network topologies, to provide detailed Layer 2 link information.

The visualization of LAG data remains integrated into the existing user interface, offering a more unified and complete view of your network.

Ease of use

GISO Support for eXR devices

This feature supports Golden ISO (GISO) upgrades for eXR devices, including ASR9000, 540X and 5501. This popular upgrade method allows users to bring routers up to date using a predefined list of SMUs in a single operation.

CSCwo82414

Kafka and NATs connectivity issues impact ISTP after applying all CAPP patch images and performing disaster restore or data restore.

CSCwp17225

In Cisco Crosswork Network Controller version 7.1.0, after performing a Geo switchover, the standby cluster's database service may fail to stream data from the active cluster, causing sync failures. This results in periodic or on-demand sync operations for database services getting stuck and remaining in the "in-progress" state for an extended duration.

CSCwp23791

5-Minute alarm auto clear job clears alarms prematurely, ignoring configured auto clear time.

CSCwp25778

Interface data settings are lost after Geo cluster switchovers.

CSCwp34475

When a distributed-cache alarm is in a Cleared state, dummy clearing events are generated on every orchestration health request for the distributed-cache pod.

CSCwp37845

The Arbitrator file upload window UI does not function correctly when using the URL option.

CSCwp59670

Alarm manual clear not working for event type SWT_AUTH_FAIL.

CSCwp84223

In high-scale environments, the Crosswork Hierarchical Controller (HCO) experiences an issue where multiple analytics topics are created because the timeout waiting for a response from the topology service (toposvc) is set too short.

CSCwp91161

Etcd lease renewals fail due to slow etcd response causing leader election lease to expire and lease renewal failures.

CSCwp93323

After enabling geographic synchronization (geo-sync) in Crosswork Workflow Manager (CWM), the service cwm-solutions-imagerepo fails to connect to the database on the standby cluster. This prevents the service from updating its database credentials, causing database connectivity issues.

CSCwq07255

While creating a 400G IP-Link service from the Hierarchical Controller Overlay (HCO), the Crosswork Network Controller (CNC) reports a bandwidth mismatch between the coherent DSP and Ethernet interfaces for the router port. Additionally, the physical connector incorrectly displays HundredGigE instead of FourHundredGigE. These inconsistencies cause the router ports to be automatically deleted from the HCO, resulting in IP Link service creation failure and no discovery of the link.

CSCwq13839

Topology links in CNC 7.0.1 show member interfaces connected to bundle interfaces, which is not a valid link.

CSCwq15192

When applying an alarms filter that includes "cleared" alarms along with other alarm types, devices with no alarms do not appear in the UI.

CSCwq16815

In a multi-vendor environment, the Crosswork Network Controller Termination Point API response does not correctly report the administrative and operational status for links connected to devices. The API returns "com:admin-state-not-applicable" and "com:oper-state-not-applicable" for these links, causing the Hierarchical Controller (HCO) to mark the link as disabled.

CSCwq31286

Error while adding additional SCP host in cross cluster storage settings in CNC 7.1 Geo HA setup.

CSCwq54679

Missing HTTP Strict Transport Security (HSTS) Policy in Crosswork Planning Platform.

CSCwq54880

Active user sessions visibility is not supported on the standby node of Crosswork Network Controller cluster.

CSCwp24902

Optima-traffic pod toggling between degraded and healthy states due to intermittent liveness check failures.

CSCwp26235

SR-PM delay and variance metrics are not displayed on UI post switchover.

CSCwp34341

SR-MPLS count remains at zero and fails to recover after geo failover. The underlying data exists in the topology service database, but it is not reflected in the UI.

CSCwp80493

Processing batch operations such as "Pause monitoring" on services while another batch operation like "Start monitoring" is still in progress may cause some services to be left in incorrect health states.

CSCwp92932

The device collection status does not move to the Maintenance status when the device is moved to the Down state.

CSCwo48615

REST API call to retrieve termination point is taking a long time in a scale environment.

CSCwp65792

The Termination API response for the QDD-OLS pluggable inserted on the device shows both the admin state and operational state as "not applicable" instead of the expected "admin-state-up" and "oper-state-up".

CSCwp84645

For higher speed interfaces (10, 25, 100 Gbps), the 'Speed' parameter in Crosswork Network Controller inventory is incorrectly populated with a fixed value of 4.29 Gbps instead of the actual interface speed.