New and Changed Information
The following table provides an overview of the significant changes to the organization and features in this guide up to this current 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 or Change |
Description |
Where Documented |
---|---|---|
Support for PAYG Licensing Model on Cisco Catalyst 8000V in Cisco Cloud APIC |
Cisco Cloud APIC supports Pay-As-You-Go (PAYG) Licensing Model on Cisco Catalyst 8000V which allows users to deploy a Catalyst 8000V instance in the cloud based on the VM size and purchase the usage on an hourly basis. |
Feature or Change |
Description |
Where Documented |
---|---|---|
Move from the Cisco Cloud Services Router 1000v to the Cisco Catalyst 8000V |
Cisco Cloud APIC moves from the Cisco Cloud Services Router 1000v to the Cisco Catalyst 8000V beginning with release 25.0(3). |
|
Terms used for Cisco Cloud Services Router 1000v and Cisco Catalyst 8000V |
The following terms are used for the two types of routers described above:
In addition, throughout this document, CCR is used as a generic term for either of the routers described above, depending on your release. |
|
Change in name of Multi-Site Orchestrator |
Cisco ACI Multi-SiteOrchestrator (MSO) has changed to Cisco Nexus Dashboard Orchestrator (NDO) beginning with the MSO release 3.4.1 on August 15, 2021. Every instance of MSO is now NDO in this Cisco Cloud APIC documentation. |
Feature or Change |
Description |
Where Documented |
---|---|---|
Support for multiple (greater than two) availability zones in AWS for Cisco Cloud APIC |
Support is now provided for multiple (greater than two) availability zones in AWS for Cisco Cloud APIC |
|
Support for configuring routing and security policies independently in AWS |
Beginning with release 25.0(2), the following updates are available for the routing policies:
|
|
CCR IPsec tunnels can now use any of the three available data interfaces for external branch connectivity |
Prior to release 25.0(2), all the tunnels to external networks are originated from one specific interface on the CCR router (the GigabitEthernet3 interface, or cloudHostIfp-2). Beginning with release 25.0(2), support is now extended where tunnels to the same destination can be formed from the GigabitEthernet2, GigabitEthernet3, and GigabitEthernet4 interfaces. This is supported for tunnels with IKEv2 configurations only. |
|
Support for increased number of cloud regions for workload deployment |
Prior to release 25.0(2), you can have a maximum of four regions per site. Beginning with release 25.0(2), you can have a maximum of sixteen regions per site. |
Feature or Change |
Description |
Where Documented |
---|---|---|
Change in release numbering for Cisco Cloud APIC |
Beginning with release 25.0(1), the release numbering has changed for Cisco Cloud APIC. The sequential order of releases for Cisco Cloud APIC is as follows:
|
|
Support for Prometheus Node Exporter on Cisco Cloud APIC |
The Prometheus Node Exporter is supported on Cisco Cloud APIC beginning with release 25.0(1). |
|
Support for IPv4 connectivity from the infra VPC CCRs to any external device with IPSec/BGP. |
Support is now available for IPv4 connectivity from the infra VPC CCRs to any external device with IPSec/BGP. |
|
Support for configuring routing policies separately, independent of security policies, between internal and external VRFs when configuring for external connectivity. |
Support is now available for configuring routing policies separately, independent of security policies, between internal and external VRFs when configuring for external connectivity. |