Cisco Network Insights for Resources Application for Cisco DCNM Release Notes, Release 2.2.2

Cisco Network Insights for Resources Application for Cisco DCNM Release Notes, Release 2.2.2

Cisco Network Insights for Resources (NIR) application consist of a pair of monitoring utilities that can be added to the Cisco Data Center Network Manager (DCNM).

This document describes the features, issues, and limitations for Cisco NIR on the Cisco DCNM.

For more information, see Related Content.

Contents

■      New Software Features

■      Open Issues

■      Resolved Issues

■      Hardware Requirements

■      Compatibility Information

■      Verified Scalability Limits

■      Usage Guidelines and Limitations

■      Related Content

■      Documentation Feedback

■      Legal Information

New Software Features

 

Note: For Cisco NIR Release 2.2.2, you must install the latest software maintainence update on Cisco DCNM Release 11.4(1). See Installing Software Maintenance Update on Cisco DCNM 11.4(1) for more information.

Open Issues

Resolved Issues

There are no resolved issues in this release.

Hardware Requirements

The Cisco NIR application supports Cisco DCNM 11.4(1) release. It is recommended to use the latest Cisco DCNM release. It is recommended to have a native HA (DCNM primary/secondary) + 3 Compute node deployment for Cisco DCNM when you want to run Cisco NIR but not mandatory.

 Hardware Requirements for Deployments up to 80 Switches and 2000 Flows

 Hardware Requirements for Deployments from 81 to 350 Switches and 12000 Flows

* A logical CPU is a Virtual CPU in a virtual hypervisor based environment and is a hyperthread in a baremetal environment.

Network card: Quad-port 10/25G

Compatibility Information

For Cisco NIR on Cisco DCNM compatibility with Day-2 Operations apps, see the Cisco Day-2 Operations Apps Support Matrix.

 

 

Note: Flow Telemetry data will consume 6MB for 10K IPv4 flows per node.

Note: Flow Telemetry data will consume 12MB for 10K IPv6 flows per node.

Verified Scalability Limits

 

Note: For fabrics greater than 150 nodes, monitored mode is recommended.

Usage Guidelines and Limitations

This section lists the usage guidelines and limitations for Cisco NIR:

■      The Cisco NIR application requires that physical servers hosting Cisco DCNM computes as VMs are atleast Cisco C220-M4 category. It is also required that a compute be hosted on a data store with a dedicated hard disk of atleast 500GB. See Hardware Requirements.

■      The Cisco NIR application supports Cisco DCNM 11.4(1) release. It is recommended to use the latest Cisco DCNM release. It is recommended to have a native HA (DCNM primary/secondary) + 3 Compute node deployment for Cisco DCNM when you want to run Cisco NIR but not mandatory. The native HA mode for Cisco DCNM is optional.

■      The Cisco NIR application installation on Cisco DCNM requires that the DNS server is valid and reachable.

■      The vPC domain ID for different vPC pair can not be the same across a fabric, when the Cisco NIR app is in managed or monitored mode on Cisco DCNM.

■      Telemetry for hardware TCAM utilization, such as forwarding TCAM and ACL TCAM are not supported on Cisco Nexus C9504, C9508, and C9516 paltform switches.

■      Cisco NIR app does not support software telemetry and flow telemetry data from switches to the flow collector running on Cisco DCNM compute nodes over IPv6.

■      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 Cisco NIR app. 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. The Cisco NIR application 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 Enviromental, Statistics, and Resources.

■      The features not supported on Cisco Nexus 7000 series switches includes Endpoint Analytics, Multicast, Microburst, CDP statistics protocol, and harware resource statistics such as COPP, HRT, LPM, QoS, and ACL.

■      The features supported on Cisco Nexus 3000 series switches includes Enviromental, 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.

■      Cisco NIR app 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.

■      In Flow Telemetry the L3-VNI flows show as L2-VNI flows when the VXLAN flow is dropped in the ingress node. When VXLAN packets are dropped in the first-hop, the exported VXLAN flow telemetry records will indicate the drop. However, they don't carry the VNI information in it. The Ingress interface from the flow telemetry export along with the VRF associated with the interface, does not deduce if the flow is L2-VNI or L3-VNI. In this case Cisco NIR app associates the L2-VNI for the flow.

■      The number of anomalies in the site dashboard will not match with the number of anomalies in the flow browse page. The site dashboard contains the total anomaly count for the time range you selected. The flow records are not aggregated in the flow browse view, where multiple flow records can point to the same anomaly entry.

■      When there are 29 million anomalies in the indices, Elasticsearch writes are too slow, which causes KAFKA lag on 350 nodes supported for Software and Hardware Telemetry. The KAFKA lag results in partial data in Cisco NIR app UI.

■      Flow Analytics information is retained for 7 days or until flow database reaches 80%, which ever happens first, then older flow analytics information is deleted from the database.

■      Cisco DCNM allows network-admin and network-operator roles to assign read or write access for fabrics. Cisco NIR app displays all the fabrics even though you do not have permission to modify. Any operation on a fabric fails without read or write access to the fabric. Cisco NIR app does not enforce the RBAC roles configured in Cisco DCNM, the operations that telemetry manager generates are filtered/enforced by Cisco DCNM according to the RBAC rules configured.

■      Cisco NIR 2.2.2 app is supported only on Cisco DCNM 11.4(1). Cisco NIR 2.2.2 app is not supported on Cisco DCNM 11.2(1) and 11.3(1).

■      In switch add cases, the software or the hardware fabric state might show the final state as Enable-failed. Under this condition the GUI might not refresh the Configuration setup page. Even though the fabric has reached a final state, the failed switch retry might be happening. In order to view the correct fabric and switch states, exit the Configuration Setup page and return back to the Setup page. Click the pending or failed switches to determine if the status has been updated from "Processing" to "Failure" or "Success" states.

■      After enabling Cisco NIR on a fabric and adding a group of switches together to the fabric, DCNM sends notification for the newly added switches. When NIR tries to program the newly added switches, DCNM can be potentially finishing the switch discovery for these switches. In this case, the NIR operation fails on the switches. The failed NIR operations should be retried with retry facility in Cisco NIR.

Related Content

The Cisco NIR documentation can be accessed from the following website:

https://www.cisco.com/c/en/us/support/data-center-analytics/network-insights-resources/model.html

The documentation includes installation, upgrade, configuration, programming, and troubleshooting guides, technical references, and release notes, as well as other documentation.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, send your comments to cisconetworkinsights-docfeedback@cisco.com.

Legal Information

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.

© 2020 Cisco Systems, Inc. All rights reserved.