Cisco Nexus Dashboard Insights Release Notes, Release 6.3.1 for Cisco ACI
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 Nexus Dashboard Insights (Nexus Dashboard Insights) service provides assurance, advisory, troubleshooting capabilities to address the operational needs of networks in a data center.
This document describes the features, issues, and limitations for Nexus Dashboard Insights on Cisco Nexus Dashboard.
For more information, see the “Related Content” section of this document.
| Date |
Description |
| January 19, 2024 |
Release 6.3.1.45 became available. |
| October 31, 2003 |
Release 6.3.1.40 became available. |
| September 13, 2023 |
Release 6.3.1.15 became available. |
Release 6.3.1.45
| Product Impact |
Feature |
Description |
| Base Functionality |
Multiple sites association for Nexus Dashboard Insights Integrations |
In this release, multiple Integrations per site are supported. |
Note: Nexus Dashboard Insights release 6.3.1.45 is only supported on Nexus Dashboard release 3.0.(1i). It is not supported on Nexus Dashboard release 3.0.1(f).
Release 6.3.1.40
| Product Impact |
Feature |
Description |
| Base Functionality |
Support for 6 node virtual Nexus Dashboard and 9 node virtual Nexus Dashboard deployment |
In this release, 6 node virtual Nexus Dashboard and 9 node virtual Nexus Dashboard deployment is supported.
|
|
|
Upgrade support for 6 node virtual Nexus Dashboard and 9 node virtual Nexus Dashboard |
In this release, 6 node virtual Nexus Dashboard and 9 node virtual Nexus Dashboard upgrade is supported. |
| Performance and Scalability |
Increased scale for 3 node physical Nexus Dashboard |
3 node physical Nexus Dashboard now supports 100 nodes and 10,000 flows |
Note: Nexus Dashboard Insights release 6.3.1.40 is only supported on Nexus Dashboard release 3.0.(1i). It is not supported on Nexus Dashboard release 3.0.1(f).
Release 6.3.1.15
| Product Impact |
Feature |
Description |
| Base Functionality |
Sustainability |
Sustainability report helps you monitor, predict, and improve your network’s energy usage, its related carbon emissions, and its total energy cost. |
|
|
Scale Conformance |
In the Conformance report, you can now view the scale conformance status for sites. |
|
|
Export Flow Records to Network Attached Storage |
You can export flow records captured by Nexus Dashboard Insights on a remote Network Attached Storage (NAS) with NFS. |
|
|
Support for -GX2 platforms |
Cisco Nexus 9300-GX2 platform switches support Software Telemetry. |
|
|
Anomaly Search |
You can perform a search for affected objects such as interface, VRF, EPG, BD and view the associated anomalies. |
|
|
Support for pure IPv6 and dual stack IPv4/IPv6 configurations |
This release adds support for pure IPv6 or dual stack IPv4/IPv6 configurations for the cluster nodes and services. |
| Ease of Use |
UI look-and-feel improvements |
This release adds product GUI improvements, including Journey Map, Global View, Analysis Hub, Custom Dashboard and more. |
| Performance and Scalability |
Connectivity Analysis |
Improved performance in Connectivity Analysis jobs. |
Release 6.3.1.40
● In this release the following features are not available:
◦ Time series selection for Interfaces, Endpoints, Multicast, and L3 neighbors.
◦ A graphical view of top resources.
● After upgrading to this release, some anomaly rules may be updated or deleted. You can manually add these rules after the upgrade based on the new categories and severity.
● After upgrading to this release, Export Data configuration will contain newer anomaly and advisory categories replacing older ones.
Release 6.3.1.15
● In this release the following features are not available:
◦ Time series selection for Interfaces, Endpoints, Multicast, and L3 neighbors.
◦ A graphical view of top resources.
● After upgrading to this release, some anomaly rules may be updated or deleted. You can manually add these rules after the upgrade based on the new categories and severity.
● After upgrading to this release, Export Data configuration will contain newer anomaly and advisory categories replacing older ones.
● Virtual Nexus Dashboard deployment for NDI release 6.3.1requires a greenfield installation of Nexus Dashboard cluster. Upgrade of virtual Nexus Dashboard cluster to run NDI release 6.3.1is not supported.
● Virtual Nexus Dashboard deployment for NDI release 6.3.1now requires reduced resources of 3 virtual nodes instead of 6 virtual nodes with lower CPU, memory, and storage needs. See Nexus Dashboard Capacity Planning for detailed support information.
● This release supports a higher number of switches on 3 node and 6 node Nexus Dashboard clusters.
◦ A 6 node Nexus Dashboard cluster with switch scale up to 500 switches for ACI and up to 350 for NDFC, supports 20,000 flows. For higher switch scale, 2,000 flows are supported.
◦ Customers having 3-5 node Nexus Dashboard cluster with up to 100 switches for ACI and up to 100 switches for NDFC needing 10,000 flow support should not upgrade to NDI release 6.3.1.
◦ See Nexus Dashboard Capacity Planning to verify the scale numbers.
This section lists the open issues in this release. Click the bug ID to access the Bug Search tool and see additional information about the caveat. The “Exists In” column of the table specifies the releases in which the issue exists.
| Bug ID |
Description |
Exists In |
| In flow analytics the health score on the flow records is displayed as healthy even when ingress flow records are not available. |
6.3.1 |
|
| In flow analytics page, PC and vPC interface ID are displayed instead of port name. |
6.3.1 |
|
| Tenant, VRF and EPG details will not be reported in Flow Browse or Details page if Q-in-Q flow is monitored using Netflow in Nexus Dashboard Insights. |
6.3.1 |
|
| If same EPG name is used across tenants in ACI sites, then flow path stitching and its details could be incorrect. This could impact forward, and reverse path stitch shown in flow pages of Nexus Dashboard Insights. |
6.3.1 |
|
| A switch reloads with a core dump of dcgrpc, dc_nae, dc, or any combination of these processes. |
6.3.1 |
|
| There is no option for enabling and disabling the NDO assurance for online sites. |
6.3.1 |
|
| Connectivity Analysis is supported on Cisco APIC release 6.0.(3e) and NICC release 3.0.0.546. |
6.3.1 |
|
| Newly discovered nodes are not visible in the Operate > Topology page. |
6.3.1 |
|
| Once the online site is onboarded to NDI, you cannot edit the username or password from the NDI UI. |
6.3.1 |
|
| The status of few devices are marked failure with reason as "ABORTED". Of these failed devices, some of them could have failed due to Log collection failure and some of them could have succeeded. |
6.3.1 |
|
| Anomalies in workflow such as NDO assurance, Delta Analysis, and Compliance may not be present in the main anomalies table due to the total number of anomalies generated hitting the maximum threshold. |
6.3.1 |
|
| Existing syslog export with SSL may be broken after Nexus Dashboard Insights (NDI) upgrade. |
6.3.1 |
|
| Configuration import for DNS configuration with mappings file is stuck in initialize state. |
6.3.1 |
|
| Cohosting of NDI and NDO on 3-node physical Nexus Dashboard cluster is not supported. |
6.3.1 |
|
| In Delta Analysis Report, resource filters added to the Grouped view of the Anomalies Table do not get carried over to the pop-up drawer containing the individual anomaly details. |
6.3.1 |
|
| The Compliance Rules tab is visible if you have at least one ACI site. |
6.3.1 |
|
| Journey Map displays blank slider after returning from Site Details. |
6.3.1 |
This section lists the resolved issues in this release. Click the bug ID to access the Bug Search tool and see additional information about the caveat. The “Exists In” column of the table specifies the releases in which the issue exists.
| Bug ID |
Description |
Fixed In |
| Scheduled jobs are queuing up in the Configure Site Group > Assurance Analysis page. |
6.3.1.15 |
|
| vPC down anomaly takes longer than 20 minutes to clear. |
6.3.1.15 |
|
| Anomalies not shown in Primary Affected Object view if the assurance job is not run in the last 2 hours. |
6.3.1.15 |
|
| As an impact of deprecation of some anomalies, Associated Policies section may not show node details for Policy CAM. |
6.3.1.15 |
|
| The anomaly details are not seen after clicking on a Flow Record Anomalies table anomaly link. |
6.3.1.40 |
|
| Flow telemetry for some records may be missing. |
6.3.1.45 |
|
| Quick add-delete of BD or VRF will lead to NetFlow not applied on the BD. |
6.3.1.45 |
|
| The records sent by the switch does not reach the collector. This issue occurs when the switch is not able to resolve the VRF ID correctly. |
6.3.1.45 |
|
| Flow telemetry information is not displayed for some nodes and telemetry records are getting dropped in NDI collector as the exporter ID does not match with the value for MO collector ID. |
6.3.1.45 |
This section lists the known issues in this release. Click the bug ID to access the Bug Search tool and see additional information about the caveat. The "Exists" column of the table specifies whether the issue was resolved in the base release or a patch release.
| Bug ID |
Description |
Exists In |
| External EPG name is not reported in Cisco Nexus Insights app even though the subnet is specified. |
6.3.1 |
|
| The EX tier-1 leaf switch is not stitched in the flow path. |
6.3.1 |
|
| In ACI platforms, with fast-link-fail over feature enabled, path summary will not have north bound or spine facing information in the flow path summary for FX2 based platforms. |
6.3.1 |
|
| When you click on Pre-Change Analysis rows in the table, if you navigate through them a bit faster without waiting for the sidebar to completely load, you may sometimes notice duplicated changes added in the form. |
6.3.1 |
|
| LLDP transmit receive packets statistics graph displays the same values regardless of the selected time range. |
6.3.1 |
|
| When L4-L7 intra VRF traffic is going through spine switches, Nexus Dashboard Insights flow path summary might not show spine switch information like spine name and interface names. |
6.3.1 |
|
| In Nexus Dashboard Insights, flow path information for L4-L7 traffic does not show the L3Out service leaf switch information. |
6.3.1 |
|
| For L3Out to EPG intra-VRF L4-L7 traffic, some of leaf switches and spine switches might not exporting flow information. Flow path will not include those nodes in the path information. |
6.3.1 |
|
| Nexus Dashboard Insights does not model Endpoint Security Groups and related rules. Stale Policy CAM rules and Enforced VRF policy violation anomaly will be displayed in Nexus Dashboard Insights |
6.3.1 |
|
| Nexus Dashboard Orchestrator job schedule and Inter-Site view in the anomaly table usability issues |
6.3.1 |
|
| vCenter anomalies are not exported as part of email export, when basic or advanced option is selected. |
6.3.1 |
|
| Since Explore is designed to support max fabric wide rules of 150k, nae-policy-explorer pod would go OOM when Explore "Connectivity analysis " is run for completed epoch having a large policy scale. |
6.3.1 |
|
| Bug Scan status will be shown as Failed with reason "CPU/Memory metrics not available for the device". |
6.3.1 |
|
| There will be an error thrown by config service if the exporters are created if the POST API is called using deprecated categories as input. |
6.3.1 |
For Nexus Dashboard Insights compatibility information see the Services Compatibility Matrix.
| Software |
Release/PID |
| Cisco Device supported for Software Telemetry |
Cisco Nexus 9300-EX, -FX, -FX2, -GX, and 9500 platform switches with EX, FX line cards Cisco Nexus 9000 FX3 and 9336C-FX2-E platform switches Cisco Nexus 9300-GX2 Platform Switches NOTE: Cisco Nexus 9300-GX2 platform switches support Flow Telemetry for the Cisco Nexus 9000 ACI-Mode Switches release 16.0(3) and later. FTE is not supported. |
| Cisco Nexus Dashboard cluster |
SE-CL-L3, ND-CLUSTER-L4 |
| Minimum Intersight Device Connector version on Cisco Nexus Dashboard |
1.0.9-828 |
| Cisco Device supported for Flow Telemetry |
Cisco Nexus 9300-EX, -FX, -FX2, -GX, and 9500 platform switches with EX, FX line cards Cisco Nexus 9000 FX3 and 9336C-FX2-E platform switches Cisco Nexus 9300-GX2 Platform Switches NOTE: Cisco Nexus 9300-GX2 platform switches support Flow Telemetry for the Cisco Nexus 9000 ACI-Mode Switches release 16.0(3) and later. FTE is not supported. |
| Minimum Cisco APIC version required for FTE and Micro-Burst |
5.1(1h) |
| AppDynamics APM |
4.5 |
For Nexus Dashboard Insights verified scalability limits see Nexus Dashboard Capacity Planning.
Rollup and Retention Numbers for Nexus Dashboard Insights Telemetry
Nexus Dashboard Insights implements a multi-level roll-up strategy for the telemetry streamed that enables better management of the data. The following table provides information about roll-up and retention policy in Nexus Dashboard Insights.
| Statistics Name |
Granularity (Time difference between sample points) |
Retention proposed for Nexus Dashboard Insights |
| Interfaces and Protocols Statistics and Error Counters |
1 minute |
3 days |
|
|
5 minutes |
7 days |
|
|
3 hours |
30 days |
| Resources and Environmental Statistics |
5 minutes |
7 days |
|
|
3 hours |
30 days |
| Integrations Statistics (AppDynamics) |
5 minutes |
7 days |
|
|
3 hours |
30 days |
| Anomalies and Advisories |
On-event* |
30 days |
| Microburst |
On-event* |
7 days |
| Endpoints History** |
On-event* |
7 days |
| Events |
On-event* |
15 days |
| Flows and Flow Telemetry Events |
- |
7 days |
| Delta Analysis |
- |
30 days |
*On-event: The data is sent from the switch or stored in the database only if the state of the object has changed.
** Endpoint History tracks the moves and modifications of an endpoint for last 7 days.
Usage Guidelines and Limitations
This section lists the usage guidelines and limitations for Cisco Nexus Dashboard Insights:
● Nexus Dashboard Insights downgrade is not supported.
● After modifying a bridge domain or VRF instance for an EPG, the flow analytics does not work as expected momentarily.
● In Multi-cluster setup, remote cluster system anomalies are not displayed in the local cluster. You must log in to the remote cluster to view the system anomalies.
● Nexus Dashboard Insights creates a user in APIC called cisco_SN_NI. This user is used when Nexus Dashboard Insights needs to make any changes or query any information from APIC. In APIC navigate to System > History > Audit Logs tab. Cisco_SN_NI user is displayed in the user column.
The Cisco Nexus Dashboard Insights documentation can be accessed from the following website:
https://www.cisco.com/c/en/us/support/data-center-analytics/nexus-insights/series.html
The documentation includes installation, upgrade, configuration, programming, and troubleshooting guides, technical references, and release notes, as well as other documentation.
| Document |
Description |
| Cisco Nexus Dashboard Insights Release Notes for Cisco ACI |
This document. |
| Cisco Nexus Dashboard Insights Deployment |
Describes how to install and upgrade Nexus Dashboard Insights. |
| Cisco Nexus Dashboard Insights User Content for Cisco ACI |
Describes the various Nexus Dashboard Insights features and use cases. |
To provide technical feedback on this document, or to report an error or omission, send your comments to ciscodcnapps-docfeedback@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: 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.
© 2021-2023 Cisco Systems, Inc. All rights reserved.
