New and changed information
The table provides an overview of the significant changes to this guide for this release. The table does not provide an exhaustive list of all changes made to the guide or of the new features up to this release.
Feature |
Description |
Where documented |
---|---|---|
Capacity Dashboard GUI enhancements |
Performance improvement and layout changes to the Capacity Dashboard GUI. |
|
Cross-launch to Nexus Dashboard cluster from APIC |
The user can directly navigate to a registered Nexus Dashboard cluster from the APIC GUI without the need for a separate login. The navigation is supported only if the Nexus Dashboard is running Release 4.1or later and the APIC is running Release 6.1.4 or later. |
Feature |
Description |
Where documented |
---|---|---|
Add node and RMA UI enhancements |
The user build a new cluster, add a node to an existing cluster, and replace one of the nodes in the existing cluster with a new node at boot using the magnetic UI. |
|
Standby APIC's |
Support for Standby APICs for APIC clusters with both physical and virtual nodes. |
Feature |
Description |
Where documented |
---|---|---|
Another round of next generation updates for the user interface |
This release introduces a preview of the next generation Cisco APIC user interface. With this preview, you can get an idea of upcoming development of the GUI. |
|
Preview of the next generation user interface |
This release introduces a preview of the next generation Cisco APIC user interface. With this preview, you can get an idea of upcoming development of the GUI. |
|
Migrating physical APICs to virtual APICs and virtual APICs to physical APICs |
You can migrate Cisco APICs from a physical APIC cluster to a virtual APIC cluster deployed on an ESXi host (using VMware vCenter), or from a virtual APIC cluster (on an ESXi host) to a physical APIC cluster. |
|
Warm standby functionality |
The warm standby functionality enables you to synchronize data when the pod or data center site is healthy. The same healthy pod or data center site is used when the pod or data center site is lost. The warm standby feature helps to synchronize the database from the other pod or data center site to the warm standby node. When a disaster occurs, the warm standby has the data and can recover the cluster without data loss. |