Cisco Nexus Dashboard Insights Release Notes, Release 6.0.2 for Cisco DCNM
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, and 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.
Note: The user content describes features, issues, and limitations for the Nexus Dashboard Insights service using the Nexus Dashboard platform with the Nexus Dashboard Fabric Controller fabric. Nexus Dashboard Fabric Controller was formerly known as Data Center Network Manager.
Cisco Data Center Network Manager (DCNM) is renamed as Cisco Nexus Dashboard Fabric Controller (NDFC) starting with Release 12.0.1a.
Note: 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.
| Date |
Description |
| February 4, 2022 |
Release 6.0.2 patch (6.0.2.1945) became available. |
| December 17, 2021 |
Release 6.0.2 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. |
| Delta Analysis enhancements |
Delta Analysis support for all types of anomalies |
| AppDynamics 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. |
| NX-OS assurance enhancements |
Prefix events support for NX-OS assurance |
| Additional pre-validation criteria for Firmware Update Analysis |
Additional pre-validation criteria such as spine redundancy check and Endpoint network redundancy for nodes for Firmware Update Analysis |
| Offline sites enhancements |
Ability to display PSIRTs, Filed Notices, and EOL advisories for offline sites. |
| VMware vCenter Integration (Beta feature) |
Add VMware vCenter integration to collect data and metrics of the virtual machines and hosts monitored by VMware vCenter. |
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 |
| Advisories are displayed for devices removed from the Site or Fabric. |
6.0.2 |
|
| Fabrics with hardware flow telemetry in disabled failed state cannot be upgraded. |
6.0.2 |
|
| After downgrading the switch to 7.0(3)I7(8) version from 9.3.5 or above, telemetry is only partially configured on the switch. |
6.0.2 |
|
| When a switch is removed from a fabric, flows records originating from that switch is displayed in Nexus Insights unless analytics feature configurations are removed. |
6.0.2 |
|
| Flow Telemetry configuration is not removed from FX3S switch if the switch was running NX-OS release 9.3.7 with Flow Telemetry enabled and then upgraded or downgraded to NX-OS release 10.1. |
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 |
|
| A duplicate or redundant switch entry may be seen on the Nodes page after the upgrade of a switch whose hostname contains a period (.) in it (eg. switch1.abc). |
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 |
|
| Flow Telemetry status shows Disabled even after enabling it in Flow settings page. |
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 |
|
| Flow statistics summary data is cleaned up after Nexus Dashboard Insights upgrade. |
6.0.2 |
|
| A system anomaly "Failed to process advisories for all devices on offline site" is raised when an offline tar file is uploaded from Cisco DCNM. |
6.0.2 |
|
| If external routes in the border leaf switch are filtered and only default route is advertised to other leaf switch via BGP EVPN VXLAN, assurance will raise anomalies for all external routes missing in the leaf switch per VRF. |
6.0.2 |
|
| OVERLAPPING_EXT_INT_PREFIX - extended support in NX-OS assurance |
6.0.2 |
|
| When a NDFC site is onboarded to Nexus Dashboard using remote authenticated users, and when Nexus Dashboard Insights is enabled on this fabric, the Nexus Dashboard Insights enable will fail. Nexus Dashboard Insights site configuration does not have the option to take in the login domain which is required for remote authenticated users. |
6.0.2 |
|
| In the Protocols Details page, port-channel listed for LLDP protocol. |
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 “Exists In” column of the table specifies the releases in which the issue exists.
| Bug ID |
Description |
Fixed In |
| 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) |
|
| 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) |
|
| Flow Telemetry status becomes disable-failed due to filter rule modify operation if a switch in the fabric has bad credentials or connectivity issues. |
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) |
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 |
| Under scale condition, when some of the flow records are either dropped in the switch or dropped in processing, partial paths will be displayed. |
6.0.2 |
|
| VRF that is associated with the NSX-V flow may not be the correct VRF the NSX-V flow is taking in the fabric. |
6.0.2 |
|
| Logical fabrics may show up in Cisco Nexus Insights. |
6.0.2 |
|
| Stopping a recurrent bug scan in log collection phase does not stop the job immediately. |
6.0.2 |
|
| Endpoint data is displayed for unsupported devices. |
6.0.2 |
|
| When Flow Telemetry is disabled while one of the switches is unreachable, the site goes into *Disable Failed* state. This is expected behavior. Following this condition, when the switch becomes available, if you enable Flow Telemetry, the ACL configurations get corrupted. |
6.0.2 |
|
| For NX-OS version 9.3(7a), Nexus Dashboard Insights is supported on DCNM release 11.5(3) and later. For DCNM release 11.5(2) release, Nexus Dashboard Insights excludes those switches from analysis resulting in partial assurance analysis for the fabric. |
6.0.2 |
|
| When there is no data coming from switches, topNodes API returns all nodes into the list as healthy with endpoint count as 0. |
6.0.2 |
For Nexus Dashboard Insights compatibility information see the Services Compatibility Matrix.
| Software/Hardware |
Release |
| Minimum Cisco NX-OS version required for Software Telemetry |
7.0(3)I7(6), 8.4(2) |
| Minimum Cisco NX-OS version required for Software and Hardware Telemetry |
7.0(3)I7(8), 9.3(2), 10.1(1), 10.2(1) |
| Minimum Cisco NX-OS version required for Host Flow Overlay |
9.3(4), 10.2(1) |
| Minimum Cisco NX-OS version required for Micro-Burst, Endpoint Analytics, and Multicast Protocols |
9.3(4) |
| Minimum Cisco NX-OS version required for Modular Hardware Telemetry |
9.3(4) |
| Minimum Cisco NX-OS version required for Connectivity Analysis |
9.3(3) |
| Minimum Intersight Device Connector version on Cisco Nexus Dashboard |
1.0.9-828 |
| Cisco Device supported for Host Flow Overlay |
Cisco Nexus 9000 -FX, -FX2, -FX3,and -GX platform switches |
| Cisco Devices supported for Flow Telemetry Events |
Cisco Nexus 9000 -FX, -FX2, -FX3, and -GX platform switches and 9700 -FX line cards |
| Cisco Device supported for Flow Telemetry |
Cisco Nexus 9000 -FX3, Cisco Nexus 9300-EX, -FX, -FX2, -FX3, and -GX platform switches and 9500-EX and FX |
| Cisco Device supported for Software Telemetry |
● Cisco Cloud Scale ASIC devices ● Cisco Nexus 7000 series switches: N77-C7710 or N77XX, N7K-C7009, N7K-C7010 or 70XX ● Cisco Nexus 3000 series switches: Nexus 3100-XL series, Nexus 3100-V series, Nexus 3200 series, Nexus 3400 series, Nexus 3500-XL series ● Cisco Nexus 9504 and 9508 with -R and -RX lines cards: ● N9K-X96136YC-R, N9K-C9508-FM-R, N9K-C9504-FM-R, N9K-X9636C-R, N9K-X9636C-RX ● Cisco Nexus 3600 platform switches: N3K-C3636C-R, N3K-C36480LD-R2, N3K-C36180YC-R ● Cisco Nexus 9000 -FX3, Cisco Nexus 9300-GX, 9300-FX3 and platform switches |
| Cisco Device not supported for Software Telemetry |
● Cisco N3K-C3408-S, N3K-C3432D-S, N3K-C34200YC-SM, N3K-34180YC, and N3K-3464C switches ● Cisco N3K-C3464C, N3K-C34180YC, N3K-C3408S, N3K-C34200YC-SM, N3K-C3432D-I |
| Micro-Burst support |
See Supported Platforms for details. |
| Arista EOS |
4.21 |
| Arista Device Supported |
Arista 7050SX and 7280SR platform switches |
Note: Flow Telemetry data will consume 6MB for 10K IPv4 flows per node. Flow Telemetry data will consume 12MB for 10K IPv6 flows per node.
| Software/Hardware |
Scale Limits |
| Number of DCNM sites |
8 for physical Nexus Dashboard |
| Maximum number of nodes supported in a site in managed mode |
150 |
| Maximum number of nodes supported across all sites |
350* * For total number of nodes greater than 150 across all sites, we recommend upgrading to Nexus Dashboard Insights release 6.2.1 |
| Maximum support for a 3-node Cisco Nexus Dashboard cluster |
Site with 50 nodes, 60000 Endpoints per Site Group, and 10000 Flows |
| Maximum support for a 6-node Cisco Nexus Dashboard cluster |
Site with 350 nodes, 60000 Endpoints per Site Group, 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, 2500 Flows, and 100000 logical rules |
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 release 6.0.1.
| 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:
● Telemetry for hardware TCAM utilization, such as forwarding TCAM and ACL TCAM are not supported on Cisco Nexus C9504, C9508, and C9516 platform switches.
● Software Telemetry telemetry should be enabled before enabling Hardware Telemetry.
● Nexus Dashboard Insights checks for metadata update every hour. However, there may not be an update every time.
● After metadata update you need to run manual bug scan to reflect PSIRTs.
● The Hardware Resources tab in System Resource Utilization Dashboard is not supported for Cisco Nexus 7000 series switches. The hardware resources do not have a direct mapping to the objects that show in Nexus Dashboard Insights. The command that shows hardware details does not provide the percentage of entries used and the maximum number of entries allocated for a particular feature. Nexus Dashboard Insights does not raise the anomalies and details page for any resource in Hardware Resources tab for Cisco Nexus 7000 series switches.
● The features supported on Cisco Nexus 7000 series switches includes Environmental, Statistics, and Resources.
● The features not supported on Cisco Nexus 7000 series switches includes Endpoint Analytics, Multicast, Microburst, CDP statistics protocol, and hardware resource statistics such as COPP, HRT, LPM, QoS, and ACL.
● The features supported on Cisco Nexus 3000 series switches includes Environmental, Statistics, and Resources.
● The features not supported on Cisco Nexus 3000 series includes Endpoint Analytics, Multicast, and Microburst.
● The IGMP and IGMP Snoop multicast statistics protocols are supported only on Cisco Nexus 9000 series switches.
● The IGMP and IGMP Snoop multicast statistics protocols are not supported for the following:
◦ Cisco Nexus 3000 and 7000 series switches.
◦ Cisco N9K-X9636C-R, N9K-X9636Q-R, N9K-X96136YC-R, and N3K-C3636C-R line cards.
● Nexus Dashboard Insights does not support BGP PrefixSaved statistics on the following:
◦ Cisco Nexus 3000, 7000, and 9000 platform switches.
◦ Cisco N9K-X96136YC-R, N9K-X9636C-R, N9K-X9636Q-R, and N3K-C3636C-R line cards.
● After enabling Nexus Dashboard Insights on a fabric and adding a group of switches together to the fabric, DCNM sends notification for the newly added switches. When Nexus Dashboard Insights tries to program the newly added switches, DCNM can be potentially finishing the switch discovery for these switches. In this case, the Nexus Dashboard Insights operation fails on the switches. The failed operations should be retried with retry facility in Nexus Dashboard Insights.
● 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.
● Flow telemetry is supported in -FX3 platform switches for the following NX-OS versions:
◦ 9.3(7) and later
◦ 10.1(2) and later
◦ Flow telemetry is not supported in -FX3 platform switches for NX-OS version 10.1(1).
● The following behaviors are observed for Nexus Dashboard Insights release 6.0.2 on Cisco Nexus Dashboard with DCNM release 11.5(2), 11.5(3), and NDFC 12.0.(2).
◦ Timeout is observed during import of large number of VRFs or networks into Nexus Dashboard Orchestrator template.
◦ If there is an inactive switch in the fabric there is a delay in deploying configuration on the switch.
◦ In large setups, in managed mode, configuration deployment from the Nexus Dashboard Insights service could take an hour or more to finish.
● The following behaviors are observed for Nexus Dashboard Insights release 6.0.2 on Cisco Nexus Dashboard with DCNM release 11.5(2) and 11.5(3).
◦ You cannot add IPv6 static route using DCNM UI in DCNM release 11.5(2) and 11.5(3).
◦ When some IPv6 Flow rules are set on Nexus Dashboard Insights, DCNM Configuration Compliance may display a persistent diff.
● If you have Nexus Dashboard Insights installed in your cluster, you must disable it before migrating from DCNM to NDFC. You can re-enable Nexus Dashboard Insights service after the migration is completed successfully. Perform the steps in the following order:
◦ Disable Nexus Dashboard Insights.
◦ Upgrade Nexus Dashboard to the latest version.
◦ Enable Nexus Dashboard Insights after the upgrade is completed successfully.
◦ Upgrade Nexus Dashboard Insights to the latest version.
◦ Disable Nexus Dashboard Insights.
◦ Perform a Backup/Restore of fabrics from DCNM 11.5.x to NDFC 12.0(2).
◦ Re-provision sites on Nexus Dashboard. (If the site name is different from the fabric name, you must remove the sites from Nexus Dashboard and add them back.)
◦ Enable Nexus Dashboard Insights.
◦ Remove sites from Nexus Dashboard Insights and add them back with the new NDFC IP address and credentials.
◦ Delete the previous Site Group and create new Site Group with same name and add the corresponding fabric to the Site Group.
● After migrating from DCNM 11.5(3) to NDFC 12.0(2), you must export Site Group configuration from Nexus Dashboard Insights to have the accurate NDFC 12.0(2) IP address and credentials during import anytime later.
● If a bug pertaining to a switch is resolved in a Software Maintenance upgrade (SMU) package, in Nexus Dashboard Insights the bug will be displayed as PSIRTs in the Advisories page.
● When you run Connectivity Analysis on a site type NDFC monitored mode, in the Nodes page, the status is displayed as Not Installed and you will not be able to upgrade the node.
● Nexus Dashboard Insights data network should be reachable to switch data and management network.
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 DCNM |
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 DCNM |
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.