Cisco Nexus Dashboard Data Broker Release Notes, Release 3.10.5
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
◦
Introduction
Visibility into application traffic is important for infrastructure operations to maintain security and compliance, and to perform resource planning and troubleshooting. With the technological advances and growth in cloud-based applications, it has become imperative to gain increased visibility into the network traffic. Traditional approaches to gain visibility into network traffic are expensive and rigid, making it difficult for managers of large-scale deployments.
Cisco Nexus Dashboard Data Broker with Cisco Nexus Switches provides a software-defined, programmable solution to aggregate copies of network traffic using SPAN or network taps for monitoring and visibility. As opposed to traditional network taps and monitoring solutions, this packet-brokering approach offers a simple, scalable and cost-effective solution well-suited for customers who need to monitor higher-volume and business-critical traffic for efficient use of security, compliance, and application performance monitoring tools.
| Date |
Description |
| June 4, 2025 |
Added CSCwo10997 to the list of Resolved Issues. |
| May 19, 2025 |
Release 3.10.5 became available. |
Salient feature(s) of the release:
| Product Impact |
Feature |
Description |
|
Base Functionailty
|
GUI support for TLS configuration |
Support for Transport Layer Security (TLS) configurations, including certificates for self-signed and third party TLS, using the Nexus Dashboard Data Broker GUI. Configuring TLS is part of device onboarding. New fields to support the TLS-related configuration have been added to the Add Device procedure. For more information, see the Devices and Administration chapter of the Cisco Nexus Dashboard Data Broker Configuration Guide, Release 3.10.5. |
Issues
Cisco Bug Search Help Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.Use the Bug Search Tool to search for a specific bug or to search for all bugs in a release.
This section includes the following topics:
● Open Issues
● Resolved Issues
● Known Issues
Open Issues
Open Issues for Cisco Nexus Dashboard Data Broker.
| Bug ID |
Description |
Exists In |
| Port-channel configuration is not getting exported. |
3.9.0 and above |
|
| Port-channel operations on ISL links results in failure of Link discovery. |
3.9.0 and above |
|
| Auto-priority connection with intersecting port range filters not working. |
3.10.0 and above |
|
| A NDB shouldn't use "session manager" way for MPLS ACLs configuration. |
3.10.0 and above |
|
| Direction change should be supported while editing span session. |
3.8.0 and above |
|
| NDB reprograms ISL ACL/ACEs without any flag enabled. |
3.10.0 and above |
|
| ISL portchannel is attached with port and global acl after upgrade from 3.7 to 3.10.1. |
3.10.1 and above |
|
| RMA of device is not getting successful on upgraded setup. |
3.10.1 and above |
|
| Adding DNAC to NDB controller fails in release 3.10.4. |
3.10.4 and above |
Resolved Issues
| Bug ID |
Description |
Resolved In |
| Device not moved to ACTIVE state, post device reload after device prerequisites configurations. |
3.10.5 |
|
| Connections disappear from usergroup connection list once modified by local user in same usergroup. |
3.10.5 |
|
| Portgroup associated connection name not getting modified after renaming the it. |
3.10.5 |
|
| ACLs not programmed correctly for auto priority connections. |
3.10.5 |
|
| NDB Match all filter should use redirect_all to include IGMP packets. |
3.10.5 |
|
| NDB Prod Switches can't be added with SSL. |
3.10.5 |
|
| Memory leak seen in NDB 3.10.4. |
3.10.5 |
|
| CLI upgrade to NDB version 3.10.4 is not working. |
3.10.5 |
|
| Log level for “updateNode” is set to info from trace in NDB 3.10.4. |
3.10.5 |
|
| NDB not able to onboard switch with NXOS version 10.4(2). |
3.10.5 |
|
| Not able to add a device to NDB with "ip name-server" CLI configured under VRF on the switch. |
3.10.5 |
|
| User with App-User role is not able to create filters and connections. |
3.10.5 |
|
| NDB going in read-only mode when APIC controller is configured with domain name. |
3.10.5 |
|
| NDB does not restore ACL configuration on the ISL interface. |
3.10.5 |
|
| NDB is not able to delete orphan ports. |
3.10.5 |
|
| Null pointer exception seen when modifying input port group. |
3.10.5 |
|
| Can not delete or edit orphan 'input ports' from NDB UI and API. |
3.10.5 |
Known Issues (NX-OS)
| Bug ID |
Description |
Exists In |
| Not seeing timestamptag on interface after configuring the cmds on C9504 platform in nxos 9.3.7. |
9.3.7 |
|
| NDB Limitation: Can't match MAC address in IP packet, it will hit deny any any in IP ACLs. |
9.2.1 and above |
|
| IP ACL with UDF match removes internal VLAN tag in Cisco NX-OS Release 9.3(2). - Fixed in 9.3(3). |
9.3.2 |
|
| Re-direct STP, CDP packets similar to LLDP port for OpenFlow. |
7.0.3 and above |
Guidelines and Limitations
This section lists the guidelines and limitations for Cisco Nexus Dashboard Data Broker:
Specific for Release 3.10.5
● The supported upgrade path is: centralized Nexus Dashboard Data Broker, Release 3.10.x to Nexus Dashboard Data Broker, Release 3.10.5 or centralized Nexus Dashboard Data Broker, Release 3.9.x to Nexus Dashboard Data Broker, Release 3.10.5.
● Communication between the Nexus Dashboard Data Broker controller and devices using OpenFlow is not supported, resulting in no support for inline monitoring.
General
● A Cisco Nexus Dashboard Data Broker instance can support only the NX-API configuration mode.
● Cisco Nexus switches managed by Cisco Nexus Dashboard Data Broker in NX-API mode must have LLDP feature enabled. Disabling LLDP may cause inconsistencies and require switch rediscovery for NX-API switches.
Compatibility Matrix
The list below contains the supported NX-OS switches for Cisco Nexus Dashboard Data Broker, Release 3.10.5. The supported mode is Tap or Span aggregation.
| Device |
Minimum Cisco Nexus Dashboard Data Broker Version |
| Cisco Nexus 3000 Series Switch Cisco Nexus 3100 Series Switch Cisco Nexus 3200 Series Switch Cisco Nexus 3164Q Series Switch |
3.0 or later |
| Cisco Nexus 31100 Series Switch |
3.7 or later |
| Cisco Nexus 9200 Series Switch |
3.1 or later |
| Cisco Nexus 9300 Series Switch |
3.0 or later |
| Cisco Nexus 9300-EX Series Switch |
3.1 or later |
| Cisco Nexus 9300-FX Series Switch |
3.5 or later |
| Cisco Nexus 9300-FX2 Series Switch |
3.7 or later |
| Cisco Nexus 9300-FX3 Series Switch
● C93180YC-FX3
|
3.10.2 or later |
| Cisco Nexus 9300-GX Series Switch |
3.10 or later |
| Cisco Nexus C9364D-GX2A Switch |
3.10.5 |
| Cisco Nexus C9332D-GX2B Switch |
3.10.2 or later |
| Cisco Nexus 9332C Switch Cisco Nexus 9364C Switch |
3.8 or later |
| Cisco Nexus 9500 Series Switch – 9504, 9508, 9516 Supported Modules:
● N9K-X97160YC-EX
● N9K-X9732C-EX
● N9K-X9732C-FX
● N9K-X9736C-EX
● N9K-X9736C-FX
● N9K-X9788TC-FX
|
3.5 or later |
Interoperability Matrix
The following table lists the hardware and software interoperability matrix for Cisco Nexus Dashboard Data Broker, Release 3.10.5.
Implementation Type: NX-API
| Device |
Supported NX-OS Versions |
| Cisco Nexus 3000 Series Switch1 – 3048, 3064 |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9). |
| Cisco Nexus 3100 Series Switch1 – 3132C-Z, 3172, 3164, 3164Q |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9). |
| Cisco Nexus 3200 Series Switch1 – 3232 |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 9.3(12). Note: NX-OS release 9.3(12) is supported only on 3232C. |
| Cisco Nexus 31100 Series Switch1 |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9). Note: NX-OS release 9.3(10), 9.3(12), is supported on 31108PCV. |
| Cisco Nexus 9200 Series Switch - C92304QC1, C92160YC Note: Cisco Nexus 9200 Series switches support only one switch deployment. |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5), 9.3(7), 9.3(7a), 9.3(8), 9.3(9),10.1(2), 10.2(2). |
| Cisco Nexus 9300 Series Switch - C93128TX1, C9396TX1 |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5) ,9.3(7), 9.3(7a), 9.3(8), 9.3(9),10.1(2), 10.2(2). |
| Cisco Nexus 9300-EX Series Switch - C93180LC-EX1, C93180YC-EX, C93108TC-EX |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5) ,9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 9.3(12), 10.1(2), 10.2(2), 10.2(3), 10.2(4), 10.2(5), 10.2(6), 10.3(2), 10.3(3). Note: NX-OS Releases, 9.3(10), 9.3(12), 10.2(4), 10.2(5), 10.2(6), 10.3(2), 10.3(3) are supported only on C93108TC-EX. |
| Cisco Nexus 9300-FX Series Switch - C93108TC-FX, C93180YC-FX |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5) 9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 10.1(2), 10.2(2), 10.2(3), 10.2(4), 10.2(5), 10.3(1), 10.3(2), 10.3(3), 10.3(6), 10.4(1), 10.4(4). Note: NX-OS Releases, 9.3(10), 10.2(4), 10.2(5), 10.3(1), 10.3(2), 10.3(3) are supported only on C93108TC-FX. |
| Cisco Nexus 9300-FX2 Series Switch - N9K-9336C-FX2, 93240YC-FX2 |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5) ,9.3(7), 9.3(7a), 9.3(8), 9.3(9), 10.1(2), 10.2(2), 10.2(3), 10.3(6), 10.4(1), 10.4(4). |
| Cisco Nexus 9300-FX2 Series Switch - C93360YC-FX2 |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5) ,9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 9.3(12), 10.1(2), 10.2(2), 10.2(3), 10.2(4), 10.2(5), 10.2(6), 10.3(1), 10.3(2), 10.3(3), 10.3(6), 10.4(1), 10.4(4). |
| Cisco Nexus 9300-FX3 Series Switch - C93180YC-FX3 |
9.3(10), 9.3(12), 10.2(4), 10.2(5), 10.2(6), 10.3(1), 10.3(2), 10.3(3), 10.3(6), 10.4(1), 10.4(4). |
| Cisco Nexus 9300-GX Series Switch - 9364C-GX,9316D-GX |
9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9), 10.1(2), 10.2(2), 10.2(3), 10.3(2), 10.4(4). Note: NX-OS Release 10.3(2) is supported only on 9364C-GX. |
| Cisco Nexus 9300-GX Series Switch - 93600CD-GX |
9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 9.3(12), 10.1(2), 10.2(2), 10.2(3), 10.2(4), 10.2(5), 10.2(6), 10.3(2), 10.3(3), 10.3(6), 10.4(1), 10.4(4). |
| Cisco Nexus 9332C Switch |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 9.3(12), 10.1(2), 10.2(2), 10.2(3), 10.2(4), 10.2(5), 10.2(6), 10.3(1), 10.3(2), 10.3(3). |
| Cisco Nexus 9364C Switch |
9.3(1), 9.3(2),9.3(3),9.3(4),9.3(5),9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 9.3(12), 10.1(2), 10.2(2), 10.2(3), 10.2(4), 10.2(5), 10.2(6), 10.3(2), 10.3(3). |
| Cisco Nexus C9364D-GX2A Switch |
10.4(4) |
| Cisco Nexus C9332D-GX2B Switch |
9.3(10), 10.2(4), 10.2(5), 10.2(6), 10.3(1), 10.3(2), 10.3(3), 10.3(6), 10.4(1), 10.4(4). |
| Cisco Nexus 9500 Series Switch Supported Modules: • N9K-X9464TX |
9.3(1), 9.3(2), 9.3(7), 9.3(7a), 9.3(8), 9.3(9), 9.3(10), 9.3(12), 10.1(2), 10.2(2), 10.2(3). 10.2(4), 10.2(5), 10.2(6), 10.3(2), 10.3(3). Note: NX-OS Releases 9.3(10), 9.3(12), 10.2(4), 10.2(5), 10.2(6), 10.3(2), 10.3(3) are supported only on 9504. |
| Cisco Nexus 9500-EX Series Switch Supported Modules: • N9K-X97160YC-EX • N9K-X9732C-EX |
9.3(1), 9.3(2), 9.3(7), 9.3(7a), 9.3(8), 9.3(9), 10.1(2), 10.2(2), 10.2(3). |
| Cisco Nexus 9500-FX Series Switch Supported Modules: • N9K-X9732C-FX |
9.3(1), 9.3(2), 9.3(7), 9.3(7a), 9.3(8), 9.3(9), 10.1(2), 10.2(2), 10.2(3), 10.3(6), 10.4(1), 10.4(4). |
Supported APIC Versions
| APIC Version |
Minimum Cisco Nexus Dashboard Data Broker Version |
Deployment Mode |
| 5.2(4d),5.2(4e), 5.2(6e), 5.3(2c) |
3.10.5 |
Centralized |
Verified Scalability Limits
The table displays the supported verified scalability limits.
| Description |
Small |
Medium |
Large |
| Number of switches used for TAP and SPAN aggegation |
25 |
50 |
75 - 100 |
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, send your comments to apic-docfeedback@cisco.com. We appreciate your feedback.
Legal Information
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: http://www.cisco.com/go/trademarks. 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. (1110R)
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 included 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.
© 2025 Cisco Systems, Inc. All rights reserved.