Cisco Nexus Dashboard Release Notes, Release 2.1.1
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 is the next generation of the Application Services Engine and provides a common platform for deploying Cisco Data Center applications. These applications provide real time analytics, visibility, and assurance for policy and infrastructure.
This document describes the features, issues, and limitations for the Cisco Nexus Dashboard software.
For more information, see the “Related Content” section of this document.
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.
This release adds the following new features:
| Feature |
Description |
| One View visibility and administration across multiple clusters |
Multiple Nexus Dashboard clusters can now be connected together for a single pane of glass view and administration of all clusters, sites, and services from any cluster in the group. For more information, see Cisco Nexus Dashboard User Guide. |
| Nexus Dashboard and services APIs |
Nexus Dashboard and Nexus Dashboard Insights APIs are now available directly in the Nexus Dashboard GUI. |
| Third-party services on Nexus Dashboard platform |
This release adds support for ServiceNow with 3rd party services integration. |
| Support for DCNM sites on Nexus Dashboard cloud clusters (AWS and Azure) |
Cisco DCNM sites can now be onboarded and managed by the cloud Nexus Dashboard clusters deployed in Microsoft Azure or Amazon Web Services (AWS). For more information, see Cisco Nexus Dashboard User Guide. |
| Dual stack IPv4 and IPv6 for management and data networks |
Nexus Dashboard management and data networks can be configured for IPv6 in addition to the IPv4 stack during cluster creation. For more information, see Cisco Nexus Dashboard Deployment Guide. |
| Increased cluster size for Nexus Dashboard deployed in VMware ESX |
Nexus Dashboard virtual clusters in VMware ESX now support up to 6 nodes (3 master and 3 worker nodes). For more information about deploying a cluster, see Cisco Nexus Dashboard Deployment Guide. For more information about extending the cluster with additional nodes, see Cisco Nexus Dashboard User Guide. |
| Co-hosting of services on virtual clusters |
Nexus Dashboard virtual clusters deployed in VMware ESX now support co-hosting of Nexus Dashboard Insights and Nexus Dashboard Orchestrator services. For more information about cluster sizing, see Nexus Dashboard Cluster Sizing tool. For more information about deploying a cluster, see Cisco Nexus Dashboard Deployment Guide. For more information about deploying services, see the service-specific documentation. |
| Node profiles for virtual nodes deployed in VMware ESX |
Nexus Dashboard virtual clusters deployed in VMware ESX now support two different node profiles: · OVA-Data -- node profile designed for data-intensive applications, such Nexus Dashboard Insights · OVA-App -- node profile designed for non-data-intensive applications, such Nexus Dashboard Orchestrator For more information about deploying a cluster, see Cisco Nexus Dashboard Deployment Guide. For more information about extending the cluster with additional nodes, see Cisco Nexus Dashboard User Guide. |
| LDAP connectivity verification |
When configuring remote authentication using LDAP servers, the UI allows you to test and verify connectivity to the LDAP server and its configuration. For more information, see Cisco Nexus Dashboard User Guide. |
| Support for Nexus Dashboard Fabric Controller service |
Starting with Nexus Dashboard, Release 2.1.1e, you can install Nexus Dashboard Fabric Controller, Release 12.0.1a in your Nexus Dashboard cluster. |
If you are installing or upgrading to this release, you must consider the following:
● If you have Nexus Insights service installed in your cluster, you must disable it before upgrading to Nexus Dashboard, Release 2.1.1 and re-enable it after the upgrade completes successfully.
● After upgrading to Release 2.1.1, we recommend upgrading all the applications to their latest versions.
● Downgrading from Release 2.1.1 is not supported.
This section lists the open issues. Click the bug ID to access the Bug Search Tool and see additional information about the issue. The "Exists In" column of the table specifies the releases in which the issue exists.
| Bug ID |
Description |
Exists in |
| All pods on node1 down. Node went into not-ready state, due to kubelet stopped pasting node status. |
2.1.1d |
|
| During ND upgrade from 2.0.2g to 2.1, elasticsearch-nir cluster was not able to get upgraded because one of its pods remained stuck in CrashLoopBackOff state. |
2.1.1d |
|
| To do upgrade ND, you need to: 1. Disable the installed apps, and 2. Validate health of the cluster before proceeding with upgrade of the a node (using acs health)
Otherwise you can end up in situations where some kafka topics will have no leader. |
2.1.1d and later |
|
| Unable to delete a security domain from site edit page. |
2.1.1d and later |
|
| After completing 2-node RMA procedure, new nodes' serial numbers are overwritten with old nodes' serial numbers, causing cluster to become unhealthy. |
2.1.1d and later |
|
| "kubectl get pods -A" reports a pod in "ContainerCreating" state. ------------------------------------------------------------------------------------- nodemgr pod/nodeagent-tbh29 0/1 ContainerCreating 0 84m <none> ute11-nd3 <none> <none>
"kubectl describe pod/nodeagent-tbh29 -n nodemgr", will have Events that look like: --------------------------------------------------------------------------------------------------------------- Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedMount 52m kubelet, ute11-nd3 Unable to attach or mount volumes: unmounted volumes=[logs], unattached volumes=[network-config localdb system-version default-token-h5npm config kms logs cloud-config]: Warning FailedMount 27m (x2 over 72m) kubelet, ute11-nd3 Unable to attach or mount volumes: unmounted volumes=[logs], unattached volumes=[kms logs cloud-config network-config localdb system-version default-token-h5npm config]: Warning FailedMount 22m (x4 over 81m) kubelet, ute11-nd3 Unable to attach or mount volumes: unmounted volumes=[logs], unattached volumes=[default-token-h5npm config kms logs cloud-config network-config localdb system-version]: Warning FailedMount 8m13s (x44 over 83m) kubelet, ute11-nd3 MountVolume.SetUp failed for volume "nodemgr-log-nodemgr" : mount command failed, status: Failure, reason: exit status 32
Keywords to look for here are: - unmounted volumes=[logs] - MountVolume.SetUp failed for volume "nodemgr-log-nodemgr" |
2.1.1d and later |
|
| You see a message like: [2021-04-13 13:48:20,170] ERROR Error while appending records to stats-6 in dir /data/services/kafka/data/0 (kafka.server.LogDirFailureChannel) java.io.IOException: No space left on device |
2.1.1d and later |
|
| Upgrade from 2.0.2h to 2.1 fails with the following message: install/1-atomix-install atomix extract failed This indicates that the 2.1 ISO was not copied completely across all nodes, and there was an IO error while trying to copy files from that ISO. |
2.1.1d and later |
|
| When worker nodes are added, some workers may get stuck in 'Discovering' state. |
2.1.1d and later |
|
| Upload of firmware image to prepare for upgrade is extremely slow. |
2.1.1d and later |
|
| One a large cluster the consolidated tech support file can become too large to fit into the file system. In this case you will notice that tech support collection failed. On this failure, you may notice that the tsctrl pod has restarted which can be observed using: "kubectl get pods -n ts" |
2.1.1d and later |
|
| Pods are stuck in "ContainerCreating" state and kubectl description of the pods will show the following errors: Warning FailedCreatePodSandBox 4m20s (x268 over 91m) kubelet, nd-node3 (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_installer-659f7846db-sc8np_installer_a4b8b47a-affd-4a87-9372-3865e82e8160_0(e3b0897ce954bb9df4a29d972d44c544ff10636f4c91a60ec55c577a5534d9e8): Multus: [installer/installer-659f7846db-sc8np]: error adding container to network "oob": delegateAdd: error invoking conflistAdd - "oob": conflistAdd: error in getting result from AddNetworkList: failed to get ippool, error: failed to get ippool, error: no such object &{10.1.1.105 {169.254.1.128 ffffff80}} NOTE: If you do not see the "failed to get ippool" error, this is not the same bug, and DO NOT APPLY WORKAROUND specified here. |
2.1.1d and later |
|
| A user may not be able to log in if they have 'approver' or 'deployer' role |
2.1.1d and later |
|
| This bug has been filed to evaluate the product against the following vulnerability in the Apache Log4j Java library disclosed on December 9, 2021 CVE-2021-44228: Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints. Cisco is currently investigating impact. For more information, see Vulnerability in Apache Log4j Library Affecting Cisco Products: December 2021. |
2.1.1d and later |
|
| When trying to add a site into Nexus Dashboard, if the password has an '&' the addition of the site fails and stays in an uknown state. With the following error message: "Site not available, Verify input:Response error:401 Unauthorized {\"totalCount\":\"1\",\"imdata\":[{\"error\":{\"attributes\":{\"code\":\"401\",\"text\":\"User credential is incorrect - FAILED local authentication\"}}}]}" |
2.1.1d and later |
This section lists the resolved issues. Click the bug ID to access the Bug Search tool and see additional information about the issue. The "Fixed In" column of the table specifies whether the bug was resolved in the base release or a patch release.
| Bug ID |
Description |
Fixed in |
| API shows active status for all the nodes, even though one node is down. |
2.1.1d |
|
| Docker registry is not cleaned up after deletion of apps. |
2.1.1d |
|
| Register link is greyed out for worker nodes and user is not able to register from UI. |
2.1.1d |
|
| Firmware activation fails with atomix-active failure as the error in the UI. |
2.1.1d |
|
| On KVM form factor if the first master is clean rebooted, the node will not recover as the certificates on the virtual device are not re-generated. |
2.1.1d |
|
| On second and third node OVA deployment, selecting "Download config from peers" does not grey out the cluster configuration fields. You do not need to fill out these fields and even if filled out, they will be ignored. |
2.1.1d |
|
| On upgrade of NAE with a larger profile, the NAE elastic search pods do not reflect the right profile values for memory and CPU. |
2.1.1d |
|
| Sites will shown in down status. This can happen for all the sites are imported. |
2.1.1d |
|
| After claiming the device, device connector shows the the connectivity is lost. In this state, check the proxy configuration and see if the proxy configuration is missing. |
2.1.1d |
|
| All pods on node1 down. Node went into not-ready state, due to kubelet stopped pasting node status. |
2.1.1e |
This section lists known behaviors. Click the Bug ID to access the Bug Search Tool and see additional information about the issue.
| Bug ID |
Description |
| For Nexus Dashboard nodes connected to Catalyst switches packets are tagged with vlan0 even though no VLAN is specified. This causes no reachability over the data network. In this case, 'switchport voice vlan dot1p' command must be added to the switch interfaces where the nodes are connected. |
|
| On power cycle system lvm initialization may fail on due to a slowness in the disks. |
|
| Upgrade fails and cluster is in diverged state with one or more nodes on the target version. |
|
| When the system is being recovered with a clean reboot of all nodes, the admin login password will be reset to the day0 password that is entered during the bootstrap of the cluster. |
|
| When bringing up ND cluster first time, all three master nodes need to join Kafka cluster before any master node can be rebooted. Failing to do so, 2 node cluster doesn't become healthy as Kafka cluster requires 3 nodes to be in Kafka cluster first time. |
|
| After ND upgrade, there will be still pods belonging to the older version running on the cluster. For example, in this case upgrade was from 2.0.1.27 to 2.0.1.36.
After the upgrade, running following command gives:
node1# kubectl get pods -n kube-system -o yaml | grep image: | grep 2.0.1.27 image: infra/ui:nd-2.0.1.27-e881b96b5 image: infra/ui:nd-2.0.1.27-e881b96b5 image: infra/ui:nd-2.0.1.27-e881b96b5 image: infra/ui:nd-2.0.1.27-e881b96b5 image: infra/ui:nd-2.0.1.27-e881b96b5 image: infra/ui:nd-2.0.1.27-e881b96b5
node1# acs version Nexus Dashboard 2.0.1.36
Clearly the ND nodes have completed upgrade, but some services are showing older version. |
|
| Pods in pending state for a long period upon restart. These pods are usually stateful sets that require specific node placement and capacity must be available on the specific node they are first scheduled. This happens when multiple applications are installed on the same ND cluster and the ND capacity overloaded. |
|
| Intersight device connector connects to the Intersight over the Cisco Application Services Engine Out-Of-Band Management. |
For Cisco Nexus Dashboard services compatibility information, see the Cisco Data Center Networking Applications Compatibility Matrix.
For Cisco Nexus Dashboard cluster sizing guidelines, see the Nexus Dashboard Cluster Sizing tool.
Physical Nexus Dashboard nodes must be running a supported version of Cisco Integrated Management Controller (CIMC).
CIMC, Release 4.2(3b) is the recommended version; CIMC, Release 4.0(1a) is the minimum supported version.
Cisco UCS C220 M3 and earlier servers are not supported for Virtual Nexus Dashboard clusters.
Nexus Dashboard clusters deployed in Linux KVM, Amazon Web Services, or Microsoft Azure support the Nexus Dashboard Orchestrator service only.
Nexus Dashboard clusters deployed in ESX VMware must use the “data” node profile if running the Nexus Dashboard Insights service.
The following table lists the maximum verified scalability limits for the Nexus Dashboard platform.
| Category |
Scale |
| Nodes in a physical cluster |
3 master nodes |
| Nodes in a virtual cluster (ESX) |
3 master nodes |
| Nodes in a virtual cluster (KVM) |
3 master nodes |
| Nodes in a cloud cluster (AWS or Azure) |
3 master nodes |
| Sites per cluster |
12 for Nexus Dashboard and Nexus Dashboard Orchestrator 4 for Nexus Dashboard Insights |
| Admin users |
50 |
| Operator users |
1000 |
| Service instances |
4 |
| API sessions |
2000 for Nexus Dashboard and Nexus Dashboard Orchestrator 100 for Nexus Dashboard Insights |
| Login domains |
8 |
| Clusters connected via multi-cluster connectivity for single pane of glass experience |
4 |
| Sites across all clusters within the same single pane of glass experience |
12 |
| Document |
Description |
| This document. Provides release information for the Cisco Nexus Dashboard product. |
|
| Provides information on physical server specifications and installation. |
|
| Provides information on Cisco Nexus Dashboard software deployment. |
|
| Describes how to use Cisco Nexus Dashboard. |
|
| API reference for the Nexus Dashboard and services. |
To provide technical feedback on this document, or to report an error or omission, send your comments to ciscodcnapps-docfeedback@cisco.com. We appreciate your feedback.
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: http://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.