Cisco Nexus Dashboard Insights Release Notes, Release 6.2.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 |
| March 27, 2023 |
Release 6.2.1 became available. |
| Product Impact |
Feature |
Description |
| Base Functionality |
Connectivity Analysis support for ACI sites |
Connectivity Analysis enables you to detect and isolate offending nodes in the network for a given flow. |
| Ease of Use |
UI enhancements |
The UI enhancements for this release includes: · Added support to include interface description in the Interfaces table. · Topology view enhancements. |
| Performance and Scalability |
Bug Scan optimizations |
Converting Bug Scan service to a dynamic service resulting in utilization of lesser resources. |
| Ease of Use |
New look and feel |
The Nexus Dashboard Insights UI has been refreshed. NOTE: Some of the existing configuration procedures in the documentation may still use the older UI screenshots and diagrams. While the look and feel of the new UI is different, the arrangement of the screens and configuration options remains the same. |
| Base Functionality |
Interface based Flow Telemetry (Beta) |
Added support to configure flow telemetry rules for interfaces such as L3Outs, SVIs, Physical Interfaces, and Port Channel. |
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.2.1 |
|
| If there is single chip spine in the flow path, then it is not reported in the flow path summary. |
6.2.1 |
|
| In flow analytics the health score on the flow records is displayed as healthy even when ingress flow records are not available. |
6.2.1 |
|
| 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.2.1 |
|
| In flow analytics page, PC and vPC interface ID are displayed instead of port name. |
6.2.1 |
|
| Aborted DAGs does not indicate that there is partial data in Nexus Dashboard Insights GUI. |
6.2.1 |
|
| Duplicate endpoint Anomalies in Nexus Dashboard Insights. |
6.2.1 |
|
| Inconsistency in counts from aggregate view to primary affected objects view for anomalies. |
6.2.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.2.1 |
|
| 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.2.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.2.1 |
|
| The anomaly record from the summary view may show the status of anomaly that is different than the one shown in Analyze page or details view. |
6.2.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.2.1 |
|
| In Nexus Dashboard Insights, flow path information for L4-L7 traffic does not show the L3Out service leaf switch information. |
6.2.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.2.1 |
|
| On a scale setup when analysis is running, sometimes anomalies and the details view has a different anomaly name for a very small set of anomalies. |
6.2.1 |
|
| Nexus Dashboard Orchestrator job schedule and Inter-Site view in the anomaly table usability issues |
6.2.1 |
|
| As part of Nexus Dashboard Orchestrator Explore workflow, in Endpoint table 'unknown epgs’ is displayed in the EPGs column. |
6.2.1 |
|
| vCenter anomalies are not exported as part of email export, when basic or advanced option is selected. |
6.2.1 |
|
| NDO Endpoints Out of Sync Between Sites anomaly is generated for a subset of endpoints even though spine switch does not have the endpoint entry in the coop table. |
6.2.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.2.1 |
|
| In the NetFlow mode, after you disable and re-enable Nexus Dashboard Insights, VRF and EPG information are not available sometimes in the flow analytics page. |
6.2.1 |
|
| Estimated Impact for BGP Prefix Received Count Fluctuation anomaly is missing |
6.2.1 |
|
| Flow Rate Statistics feature under System Status Page can sometimes have empty Node Flow Rate tables. |
6.2.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.2.1 |
|
| A switch reloads with a core dump of dcgrpc, dc_nae, dc, or any combination of these processes. |
6.2.1 |
|
| As an impact of deprecation of some anomalies, Associated Policies section may not show node details for Policy CAM. |
6.2.1 |
|
| Scheduled jobs are queuing up in the Configure Site Group > Assurance Analysis page. |
6.2.1 |
|
| For assurance anomalies, the primary affected objects are not displayed in the aggregated view. |
6.2.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 "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 |
| Assurance anomalies are not exported as part of email export, when basic or advanced option is selected. |
6.2.1 |
|
| Bug Scan feature may identify issues that have already been resolved in Cisco Nexus 9000 ACI-mode switch release 16.0(2h). |
6.1.3 |
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.2.1 |
|
| The EX tier-1 leaf switch is not stitched in the flow path. |
6.2.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.2.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.2.1 |
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, 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 |
| 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 Dashboard |
| Number of ACI nodes (includes ACI switches) |
500 for physical Nexus Dashboard 50 for virtual Nexus Dashboard |
| 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 support for a 9-node Cisco Virtual Nexus Dashboard (vND) cluster (3 data nodes and 6 app nodes) |
Site with 200 nodes, 5000 Endpoints per Site Group and 20000 per cluster, 5000 Flows, and 100000 logical rules |
| Maximum number of leaf switches in a POD running PTP |
128 288 for APIC release 5.2(5) and later |
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-premises 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.
● 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.
● If you have not configured persistent IP addresses in Nexus Dashboard, you will receive the following error message:
utr and collectorpersistent services not in desired state
This error message has no functional impact and you can either ignore the error message or add 7 persistent IP addresses after the cluster is deployed using the External Service Pools configuration in the Nexus Dashboard UI, as described in the Cisco Nexus Dashboard User Guide. After allocating the persistent IPs, you must disable and enable Nexus Dashboard Insights.
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-2023 Cisco Systems, Inc. All rights reserved.
