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.
This chapter provides release-specific information for each new and changed feature in the .
The table below summarizes the new and changed features for the Cisco APIC-EM Release 1.2.0.x that are covered in this document. For information about all of the features in the release, see the Release Notes.
Feature |
Description |
Where Documented |
||
---|---|---|---|---|
New Home page view with system health data displayed |
New Home page view, with Home and System Health tabs. |
See Chapter 6, Configuring the Cisco APIC-EM Settings. |
||
New TLS version support for the controller. |
You can configure the TLS version for communications for northbound API connections to the controller using a CLI command run on the host. |
See Chapter 3, Cisco APIC-EM Security. |
||
New configuration options available for inter-host communications within a multi-host cluster. |
You can configure IPSec tunneling for communications between the hosts using the configuration wizard during a deployment or an upgrade. You can also configure IPSec tunneling for communications between hosts with a new CLI command. The default for inter-host communications is GRE.
|
See Chapter 3, Cisco APIC-EM Security and Chapter 5, Deploying the Cisco APIC-EM. |
||
New external authentication support for the controller. |
You can configure the controller to access and communicate with an AAA server using the RADIUS protocol. This enables a user to login into the controller using the credentials on an AAA server. |
See Chapter 6, Configuring the Cisco APIC-EM Settings. |
||
New Cisco APIC-EM evaluation version is available. |
An evaluation version of the Cisco APIC-EM is provided for a host with 16 to 25 GB of memory. |
An evaluation version of the Cisco APIC-EM is provided with this release. The Cisco APIC-EM evaluation version can be deployed on a host (appliance, server, or virtual machine) that has only 16 GB of memory. The Cisco APIC-EM evaluation version provides all of the features of the standard version, with the following limitations:
Telemetry is not supported.
Logging has reduced functionality.
Maximum number of devices supported for the controller is 20.
Cisco APIC-EM will discover your host's available memory during the deployment process and will provide the following responses and options:
When deploying the controller on a host with 64 GB or more of memory (meets the memory requirements), the configuration wizard will proceed with the installation.
When deploying the controller on a host with 25 to 64 GB of memory, you are prompted to add another host or increase memory on the host to meet the requirements.
When deploying the controller on a host with 16 to 25 GB or memory, you are prompted to install a low-memory, evaluation version of the controller.
When deploying the controller on a host with less than 16 GB of memory, you are prompted to add more memory and cannot proceed with the installation.
Note | The deployment process for the evaluation version is the same as the deployment process for the standard single host. |