Nexus Dashboard Insights Release Notes, Release 6.4.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 7, 2024 |
Release 6.4.1.45 became available. |
| Product Impact |
Feature |
Description |
| Base Functionality |
Panduit integration |
Panduit Power Distribution Unit (PDU) Integration in Nexus Dashboard Insights enables you to monitor energy usage and unlock sustainability insights for sites and individual devices connected to a Panduit PDU. |
|
|
Multi-cluster view |
You can consolidate multiple Nexus Dashboard clusters into a single Global View. |
|
|
Time range selection |
You can now select a time range in the Site View. |
|
|
LACP/PIM/IGMP/IGMP-Snooping, and OSFP protocol support |
LACP, PIM, IGMP, IGMP-Snooping, and OSPF protocols for switches are now supported. |
|
|
New Bug Scan in Analysis Hub |
You can now view the active and susceptible bugs affecting your network after the Bug Scan is completed in Analysis Hub. |
|
|
Real-time telemetry (interfaces, hardware stats and more) |
Real Time Visualization (RTEV) feature facilitates real-time event rendering within a user interface (UI) environment. |
| Ease of Use |
Compliance rule description and custom recommendations |
You to now add a custom description when a compliance rule is created. |
|
|
Health resource enhancements in Delta Analysis |
Delta Analysis now performs an object delta rather than a count delta. So along with the count, you can now view how many anomalies were cleared, how many are unchanged and how many are new anomalies. |
|
|
Compliance report new UI |
A new user experience for easier visibility of communication and configuration compliance. |
| Performance and Scalability |
Connectivity Analysis improved job times |
The time taken by the connectivity analysis jobs in Nexus Dashboard Insights has been reduced. |
|
|
Large file support for Bug Scan |
Support for large files for Bug Scan. |
|
|
1-node Nexus Dashboard support for Insights |
This release supports 1-node physical Nexus Dashboard cluster for Insights. |
|
|
Increased scalability for NDI co-hosted with NDFC in a 3 node pND cluster (250 switches) |
NDI co-hosted with NDFC in a 3 node physical Nexus Dashboard cluster now supports 250 switches. |
● Beginning with Nexus Dashboard release 3.1(1), all services have been unified into a single deployment image. You no longer need to download, install, and enable each service individually. Instead, you can simply choose which services to enable during the Nexus Dashboard platform deployment process. As a result, we recommend deploying Nexus Dashboard release 3.1(1) with unified install for all new installations. Upgrading to this release will also automatically upgrade all services in your existing cluster. See Nexus Dashboard Deployment Guide.
● The left navigation menu options Operate and Configure are now merged into Manage menu option.
In Nexus Dashboard, navigate to Admin > System Settings > General > External Service Pools > Add Data Service IP Address to configure the persistent IP address.
For more information on persistent IP address requirements, see Cisco Nexus Dashboard and Services Deployment and Upgrade Guide.
Open Issues
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 |
| 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.4.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.4.1 |
|
| A switch reloads with a core dump of dcgrpc, dc_nae, dc, or any combination of these processes. |
6.4.1 |
|
| Connectivity Analysis is supported on Cisco APIC release 6.0.(3e) and NICC release 3.0.0.546. |
6.4.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.4.1 |
|
| Existing syslog export with SSL may be broken after Nexus Dashboard Insights (NDI) upgrade. |
6.4.1 |
|
| When running "show environment power" there is no power consumption reported for the FAN for 1 rack unit and 2 rack units switches. |
6.4.1 |
|
| When you enable flow telemetry, the status for the site will not be changed to "Enabling" immediately. |
6.4.1 |
|
| Duplicate BGP Peer connection down anomaly is raised for same peer. |
6.4.1 |
|
| Super Spine is not counted under objects in Topology view. |
6.4.1 |
|
| In the Policy CAM Anomalies table, when you click on the gear icon and select Category it does not get added to the Anomalies table. |
6.4.1 |
|
| While creating a compliance rule, the following error message is displayed: "The Assurance Group ID <id> is invalid." |
6.4.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 |
| Newly discovered nodes are not visible in the Operate > Topology page. |
6.4.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.4.1 |
|
| Configuration import for DNS configuration with mappings file is stuck in initialize state. |
6.4.1 |
|
| Cohosting of NDI and NDO on 3-node physical Nexus Dashboard cluster is not supported. |
6.4.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.4.1 |
|
| The Compliance Rules tab is visible if you have at least one ACI site. |
6.4.1 |
|
| Journey Map displays blank slider after returning from Site Details. |
6.4.1 |
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.4.1 |
|
| The EX tier-1 leaf switch is not stitched in the flow path. |
6.4.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.4.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.4.1 |
|
| LLDP transmit receive packets statistics graph displays the same values regardless of the selected time range. |
6.4.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.4.1 |
|
| In Nexus Dashboard Insights, flow path information for L4-L7 traffic does not show the L3Out service leaf switch information. |
6.4.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.4.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.4.1 |
|
| Nexus Dashboard Orchestrator job schedule and Inter-Site view in the anomaly table usability issues |
6.4.1 |
|
| vCenter anomalies are not exported as part of email export, when basic or advanced option is selected. |
6.4.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.4.1 |
|
| Bug Scan status will be shown as Failed with reason "CPU/Memory metrics not available for the device". |
6.4.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.4.1 |
|
| In flow analytics the health score on the flow records is displayed as healthy even when ingress flow records are not available. |
6.4.1 |
|
| In flow analytics page, PC and vPC interface ID are displayed instead of port name. |
6.4.1 |
|
| Once the online site is onboarded to NDI, you cannot edit the username or password from the NDI UI. |
6.4.1 |
|
| There is no option for enabling and disabling the NDO assurance for online sites. |
6.4.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. |
| 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.
