Cisco Nexus Dashboard Insights Release Notes, Release 6.0.2 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 |
| February 4, 2022 |
Release 6.0.2 patch (6.0.2.1945) became available. |
| December 17, 2021 |
Release 6.0.2 (6.0.2.1928) became available. |
| Feature |
Description |
| DNS Integration |
Use DNS Integration to enable the name resolution feature to telemetry data. |
| Flow Rate Statistics
|
Figure out the incoming flow rate for your specific setup by viewing the incoming pipeline rates for the fabric and at the per switch level. |
| New Hardware support |
Support for Nexus 9000 FX3 and 9336C-FX2-E platform switches. Note: Nexus Dashboard Insights, release 6.0.2 supports Cisco Nexus 9000 FX3 platform switches only in fabrics running Cisco APIC release 5.2(4) or later. |
| Delta Analysis enhancements |
Delta Analysis support for all types of anomalies |
| AppDynamic SaaS integration support |
Ability to connect to AppDynamics controller using a proxy for SaaS or cloud deployments. |
| Digitize advisories |
Digitize release notes, field notices, and EOL/EOS advisories. |
| Risk and Conformance report |
Configure software and hardware conformance report. |
| Additional pre-validation criteria for Firmware Update Analysis |
Additional pre-validation criteria such as Endpoint network redundancy for nodes for Firmware Update Analysis. |
| Offline sites enhancements |
Ability to display PSIRTs, Filed Notices, and EOL advisories for offline sites. |
| Export Data enhancements |
Collect data for specific resources at a greater frequency and export it directly. Note: Export data enhancements is supported only in fabrics running Cisco APIC release 5.2(4) or later. |
| Template Based Compliance |
Configure a template and specify types of queries to select objects and attributes that enforce specific conditions when enabled. |
| Configure Object Selectors for Naming Compliance |
Configure a Naming Compliance to match selected objects using a template. |
| Configure Object Selectors Based on Tags and Annotations |
Configure object selectors on tags and annotations using a template. |
| Cisco Nexus Dashboard Orchestrator Integration and Assurance (Beta feature) |
Add Nexus Dashboard Orchestrator integration to enable and run assurance analysis for managed sites and Site Groups. |
| VMware vCenter Integration (Beta feature) |
Add VMware vCenter integration to collect data and metrics of the virtual machines and hosts monitored by VMware vCenter. |
The endpoint information is no longer included in the Tenant file size calculation. This does not remove any capability from the Pre-Change Analysis feature.
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 |
| LLDP transmit receive packets statistics graph displays the same values regardless of the selected time range. |
6.0.2 |
|
| If there is single chip spine in the flow path then it is not reported in the flow path summary. |
6.0.2 |
|
| In flow analytics the health score on the flow records is displayed as healthy even when ingress flow records are not available. |
6.0.2 |
|
| After reaching the 500 flows limit, any extra flows will not be reported. These un-programmed extra flows will not be reported even when we delete few of the programmed flows. |
6.0.2 |
|
| In flow analytics page, PC and vPC interface ID are displayed instead of port name. |
6.0.2 |
|
| A duplicate or redundant switch entry may be seen on Nodes page after upgrade of a switch whose hostname contains a period (.) in it (eg. switch1.abc). |
6.0.2 |
|
| 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.0.2 |
|
| Site becomes "Disabled" or "Add_Fail" and policies will not be pushed to the fabric when Nexus Dashboard Insights gets disabled and re-enabled or upgraded if the site goes down. |
6.0.2 |
|
| Selecting a time range of Last Week on the Interfaces Dashboard causes the browser to show a blank screen. |
6.0.2 |
|
| Aborted DAGs does not indicate that there is partial data in Nexus Dashboard Insights GUI. |
6.0.2 |
|
| Duplicate endpoint Anomalies in Nexus Dashboard Insights. |
6.0.2 |
|
| Assurance job is aborted if there is not enough CPU and memory resources available and if there are multiple jobs running at the same time. |
6.0.2 |
|
| Inconsistency in counts from aggregate view to primary affected objects view for anomalies. |
6.0.2 |
|
| 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.0.2 |
|
| Flow statistics summary data is cleaned up after Nexus Dashboard Insights upgrade. |
6.0.2 |
|
| The Explorer "Can" query, "Can EPG:A talk to EPG:B?" may sometimes include in the Policy Table additional incorrect rules as the ones allowing the communication. However, the correct rule that allows the communication is always present in the table. |
6.0.2 |
|
| In Configuration export import feature, the following configurations are not supported only during the IMPORT.
● Template based Compliance Configuration and
● Compliance configuration by importing JSON/Xml file
|
6.0.2 |
|
| The anomaly record from the summary view may show the status of anomaly that is different than the one shown in analyze pane or details view. |
6.0.2 |
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 "Fixed In" column of the table specifies whether the issue was resolved in the base release or a patch release.
| Bug ID |
Description |
Fixed In |
| The total count of anomalies reported in the Overview > Dashboard's page for Alerts Summary, Anomalies Breakdown, and Top Nodes tiles sometimes do not match. |
6.0.2 (6.0.2.1928) |
|
| The Netflow Collector IP addresses reported on the Configure Site Group Flows tab in Nexus Dashboard Insights are for Multi-cluster Connectivity primary Nexus Dashboard cluster IP addresses instead of the Site Group's own Nexus Dashboard cluster IP addresses. |
6.0.2 (6.0.2.1928) |
|
| Evaluation of Nexus Dashboard Insights for Log4j RCE (Log4Shell) Vulnerability. |
6.0.2 (6.0.2.1928) |
|
| If a Site Group is used in an integration and after a successful integration is created, if Site Group name is changed that name change will not be reflected when a GET call is made for integrations. |
6.0.2 patch (6.0.2.1945) |
|
| If the compliance template does not detect any violations, it will raise an event for the root object only. In the case of some configurable managed objects such as fabric and infra, info anomaly will be raised. |
6.0.2 patch (6.0.2.1945) |
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 |
| Cisco NIA allows onboarding of third party sites without any devices being discovered. |
6.0.2 |
|
| External EPG name is not reported in Cisco Nexus Insights app even though the subnet is specified. |
6.0.2 |
|
| The EX tier-1 leaf switch is not stitched in the flowpath. |
6.0.2 |
|
| In the Flow analytics details page, path information might not display spine node in the traffic path. |
6.0.2 |
For Nexus Dashboard Insights compatibility information see the Services Compatibility Matrix.
| Software |
Release/PID |
| Cisco Device supported for Software Telemetry |
Cisco Nexus 9000 Series switches |
| Cisco Nexus Dashboard cluster |
SE-CL-L3 |
| 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 |
| Minimum Cisco APIC version required for FTE and Micro-Burst |
5.1(1h) |
| AppDynamics APM |
4.5 |
| Software/Hardware |
Scale Limits |
| Number of ACI sites |
8 for physical Nexus Dashboard 4 for virtual Nexus Dashbooard |
| Number of ACI nodes (includes ACI switches) |
500 for physical Nexus Dashboard 50 for virtual Nexus Dashbooard |
| Maximum support for a 3-node Cisco Nexus Dashboard cluster |
Site with 50 nodes, 60000 Endpoints per Site Group and 100000 per cluster, and 10000 Flows |
| Maximum support for a 4-node Cisco Nexus Dashboard cluster |
Site with 100 nodes, 60000 Endpoints per Site Group and 140000 per cluster, and 10000 Flows, and 300000 logical rules |
| Maximum support for a 6-node Cisco Nexus Dashboard cluster |
Site with 500 nodes, 60000 Endpoints per Site Group and 200000 per cluster, 20000 Flows, and 300000 logical rules |
| Maximum support for a 6-node Cisco Virtual Nexus Dashboard (vND) cluster |
Site with 50 nodes, 5000 Endpoints per Site Group and 20000 per cluster, 2500 Flows, and 100000 logical rules |
| Maximum number of leaf switches in a POD running PTP |
128 |
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.
● When the Device Connector is unclaimed from the on-premise GUI application, the Device Connector must be unclaimed from Intersight for TAC Assist’s connected TAC functionality to work.
● After modifying a bridge domain or VRF instance for an EPG, the flows show errors and flow analytics does not work as expected.
● For virtual Nexus Dashboard (vND), you must provision the underlying HOST with Distributed Virtual Switch and not with a Standard Virtual Switch.
● Nexus Dashboard Insights release 6.0.2 supports Kafka export for Flow anomalies. However, Kafka export is not currently supported for Flow Event anomalies.
● 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.
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 Guide |
Describes how to install and upgrade Nexus Dashboard Insights. |
| Cisco Nexus Dashboard Insights User Guide for Cisco ACI |
Describes how to use Nexus Dashboard Insights. |
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-2022 Cisco Systems, Inc. All rights reserved.
