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 contains the following sections:
The following table provides an overview of the significant changes to this guide for this current release. The table does not provide an exhaustive list of all changes made to this guide or of all new features in this release.
Feature |
Description |
Where Documented |
---|---|---|
VM Naming Conventions |
Specific naming convention is followed for the VM names when application is provisioned for the private network or when adding VMs to an APIC container. |
Creating an Application Container Using a Template, Adding VMs |
Support of ASAv9.3.2 |
You can choose the deployment option using which VM can be deployed. The deployment options are listed based on the OVF for ASAv 9.3.1, ASAv 9.3.2, and later. |
|
Stateful ASA Failover |
The configuration of a Cisco ASA firewall in high availability mode now supports stateful failover for the Cisco ASA. Stateful failover ensures that the active unit continually passes per-connection state information to the standby unit. If a failover occurs, this configuration ensures that the same connection information is available at the new active unit. |
|
Support for Multi-Context Configuration |
Layer 4 to Layer 7 policy must accommodate multiple contexts configurations on the ASA devices. |
|
Support for advanced load balancer parameters |
Network device system parameter policy sets the NTP and SNMP parameters that are needed to be configured on a load balancer device. |
|
SSL Offload Support |
The L4-L7 Policy for a load balancer now supports SSL offloading as well as basic load balancing through HTTP. SSL offloading moves the processing of SSL encryption and decryption from the main Web server to a separate device designed for that task. This features increases the performance of the Web server and improves the efficiency of SSL certificate handling. During deployment of an application container, you must provide an SSL certificate for the SSL offloading. |
|
Dynamic Subnet Size per Tier |
The maximum number of VM instances per tier allows you to determine the subnet size for each tier. |
|
Support for Tags in Datastore |
You can choose the tag values for each tier. During container provisioning, resource is selected based on the tag associated with the tier. |
|
Application Profile Support for Hyper-V |
You can also perform a container provisioning in the Hyper--V environment. |
|
Shared L3Out Feature |
To integrate the ACI fabric with shared external Layer 3 network. The network must be tagged and updated on Tenant vPOD in advance and the same tag must be selected for the external network in case of shared L3Out. |
|
Loadbalancer vServer Support |
The application container has the ability to view, add, or delete the load balancer L4-L7 services. The newly created VMs are added as real servers to the L4-L7 service . |
|
Contract between Different Containers |
You can view and add the contract between tiers of different containers in Cisco UCS Director. You need to drill down each contract to view all the security rules created for each application container in Cisco UCS Director. |
|
Add vNIC to Container VM |
You can add vNIC to the container VM for private network communication between VMs belonging to same network zone. |
|
Container to show Virtual Routing and Forwarding instance |
Added Virtual Routing and Forwarding (VRF) instance in the Tier summary of the Container report. |