Cisco Nexus Insights Release Notes, Release 5.1(0) 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 Insights (NI) application consist of a monitoring utility that can be added to the Cisco Application Centric Infrastructure (ACI).
This document describes the features, issues, and limitations for Cisco Nexus Insights (NI) on Cisco Nexus Dashboard.
For more information, see Related Content
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 |
| June 10, 2021 |
Release 5.1(0) patch (5.1.0.135) became available. |
| April 27, 2021 |
Release 5.1(0) (5.1.0.131) became available. |
| Feature |
Description |
| Cisco Nexus Dashboard support |
Cisco Nexus Insights app can be deployed as a service on Cisco Nexus Dashboard. |
| Multi-Site |
Monitor multiple sites with single instance of Cisco Nexus Insights. |
| UI enhancements |
Improved design with a streamlined tabbed layout, enhanced options for selecting a time range, centralized summary of sites with All Sites Dashboard, detect and indicate when features are not supported by a node. |
| Cisco Nexus Insights app unification |
Integrating Cisco NIR and Cisco NIA apps into Cisco NI app to get anomalies, advisories, and functionalities such as scheduling log collection jobs, scheduling bug scan and compliance jobs, firmware upgrade paths, and recommendations for upgrade versions. It also includes in-depth analysis work flows for advisories and anomalies. |
| Topology View |
Visualize logical constructs such as Tenant, VRF, EPG and more on top of physical topology. Perform rapid troubleshooting using filters to focus on problematics nodes. |
| Cisco Nexus Insights Independence |
Cisco NI app collects the node capabilities to determine and display the features supported and features not supported for each node on the site. |
| Micro-Burst detection |
Expose and locate invisible microbursts. Know the congestion hot spots and protect application performance. Microburst is supported on APIC release 5.1(1) and later. |
| Cisco ACI 3-Tier support |
Monitor Cisco ACI multi-tier topology with Cisco Nexus Insights features and functions. |
| Flow Telemetry Events |
Use flow table events to minimize troubleshooting time through automated root-cause analysis of data plane anomalies, such as routing issues, ACL drops, buffer drops and more. |
| Kafka messaging support |
Share Cisco Nexus Insights enriched value-added output with application ecosystem. Build synergetic workflows with third party IT applications. |
| Email notification support |
Get offline alerts about network health using email notification facility. Pick and choose which issues you need to be alerted about. |
| PSIRT notification and Defect notification |
Detect vulnerability exposure with PSIRT scan. Detect exposure to known defects with defect scan. |
| Resources |
Monitor capacity utilization changes and threshold violations with resource anomalies. |
| Statistics |
View control plane, data plane statistics, detect control plane and data plane anomalies. |
| Support for Cisco Nexus 9300-GX series switches |
Monitor your high performance, scalable data center with support for Cisco Nexus 9300-GX series 400 GE platform switches. |
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. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Flow resource type anomalies are not exported to external kafka server. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Endpoint is reported as aged-out with the older BD information. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Rogue IP anomaly is not raised for every leaf switch. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Rogue IP anomaly is not cleared. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Navigating from an interface down anomaly might sometimes take you to the interface details with the wrong time range so it will show the reported anomaly on the interface detail. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Microburst Anomaly's description field does not contain class and type of traffic information. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| If there is single chip spine in the flow path then it is not reported in the flow path summary. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| In flow analytics the health score on the flow records is displayed as healthy even when ingress flow records are not available. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| 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. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| In flow analytics page, PC and vPC interface ID are displayed instead of port name. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Multiple operational anomalies are reported for same resource. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| The creation time for the ‘Leaf Inactive’ Fault is incorrect in the Cisco NI app GUI. |
Cisco Nexus 9000 ACI-Mode Switches Release 15.1.2 |
|
| Bug scan fails resulting in BORG error. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| When the Infrastructure is down, the job termination action cannot be completed and results in some Bug Scan jobs to be in the "in-progress" state. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| In the Nexus Insights setup page, clicking the Prerequisites checkbox resets the Early Access Mode toggle. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| When you start a bug Scan, the History table is not updated and the Scan Now button is not disabled. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| L3 Multicast control plane data is not supported for Remote Leaf in Cisco NIR. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Some IPv6 traffic will not be reported to telemetry collectors. |
Cisco Nexus 9000 ACI-Mode Switches Release 15.1.3, 15.1.4 |
|
| Metadata update task is not scheduled on app startup if the fabric is not enabled. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| When you onboard a new site to Nexus Dashboard, the site does not appear in Nexus Insights UI. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| ACI FN-72145 is displayed for switch running standalone NX-OS in DCNM fabric. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| Internal database system experienced out of memory . Streaming data will not be retrieved or saved after and during the time internal database component recovers completely and becomes stable. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
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 |
| Bug scan borg partial failure in a resource intensive scale environment. |
5.1(0) (5.1.0.131) |
|
| When we enable and disable multicast (PIM) on a BD, the IGMP IFstats MO is not cleared and is displayed as a blank entry in Cisco NI. |
Cisco Nexus 9000 ACI-Mode Switches Release 15.1.2 |
|
| Spine switches s are not reported in flow analytics after VRF, BD, EPG change. |
Cisco Nexus 9000 ACI-Mode Switches Release 15.1.2 |
|
| Flow Telemetry is not exported for IPv6 rules for tier-1 leaf switches. |
Cisco Nexus 9000 ACI-Mode Switches Release 15.1.2 |
|
| After you disable and enable the Cisco NI App, spine switches does not export flows. |
Cisco Nexus 9000 ACI-Mode Switches Release 15.1.2 |
|
| Spine switches does not report the flows to NI collector. |
Cisco Nexus 9000 ACI-Mode Switches Release 15.1.2 |
|
| Collection Status for flows and endpoints is reported as "Feature not supported" in the GUI. |
5.1(0) patch (5.1.0.135) |
|
| When leaf switch becomes inactive because of unreachability both node reload and node inactive anomaly are raised though only node inactive anomaly is expected. |
5.1(0) patch (5.1.0.135) |
|
| In the System Status page, when you use the filter, some options do not display the results acuurately. |
5.1(0) patch (5.1.0.135) |
|
| AppD stdout / stderr logs are copied to /opt/telegraf/log/ in the telegraf container. and are not log rotated. As a result, over a period, storage space may run out in telegraf and AppD data collection process potentially gets stuck. |
5.1(0) patch (5.1.0.135) |
|
| Even when the switches are streaming flow information, flows are not processed and no flows are visible in the UI. |
5.1(0) patch (5.1.0.135) |
|
| Time Window sets incorrect date when the user modifies the date and time. |
5.1(0) patch (5.1.0.135) |
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. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| External EPG name is not reported in Cisco Nexus Insights app even though the subnet is specified. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| The EX tier-1 leaf switch is not stitched in the flowpath. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
|
| In the Flow analytics details page, path information might not display spine node in the traffic path. |
5.1(0) and 5.1(0) patch (5.1.0.131 and 5.1.0.135) |
For Cisco NI on Cisco ACI and Cisco NI on Cisco Nexus Dashboard compatibility with Day-2 Operations apps see the Cisco Data Center Networking Applications 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-737 |
| Cisco Device supported for Flow Telemetry |
Cisco Nexus 9300-EX, -FX, -FX2, -GX, and 9500 platform switches with EX, FX line cards |
| Minimum Cisco APIC version required for FTE and Micro-Burst |
5.1(1h) |
| AppDynamics APM |
4.5 |
| Software/Hardware |
Scale Limits |
| Number of ACI fabrics |
8 |
| Number of ACI nodes (includes ACI switches) |
500 |
| Number of flows supported in Flow Analytics |
20000 |
| Maximum support for a 3-node Cisco Nexus Dashboard cluster |
Fabric with 50 nodes, 60000 Endpoints, and 10000 Flows |
| Maximum support for a 4-node Cisco Nexus Dashboard cluster |
Fabric with 100 nodes, 60000 Endpoints, and 10000 Flows |
| Maximum support for a 6-node Cisco Nexus Dashboard cluster |
Fabric with 500 nodes, 60000 Endpoints, and 20000 Flows |
Usage Guidelines and Limitations
This section lists the usage guidelines and limitations for Cisco NI app:
● Cisco NI 5.1(0) app 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 Assit’s connected TAC functionality to work.
● You have to configure telemetry in the Cisco NI app to configure for fabric node control.
● 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.
● If you are deploying Multi-Site Orchestrator, Nexus Insights, and Network Assurance Engine in the same cluster, you must ensure that Nexus Insights and Network Assurance Engine are installed and enabled first before enabling the Multi-Site Orchestrator application.
The Cisco NI 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 Insights Release Notes for Cisco ACI |
This document. |
| Cisco Nexus Insights User Guide for Cisco ACI |
Describes how to download, install, and set up Cisco NI app. |
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 Cisco Systems, Inc. All rights reserved.