New and Changed Information

This chapter contains the following sections:

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.

Table 1. New Features and Changed Behavior in Cisco Cloud APIC for Release 25.0(4)

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.

Table 2. New Features and Changed Behavior in Cisco Cloud APIC for Release 25.0(3)

Feature or Change

Description

Where Documented

Support for multiple frontend IP addresses for Azure network load balancer

This release provides support for multiple frontend IP addresses for the Azure network load balancer in Cisco Cloud APIC.

Deploying Layer 4 to Layer 7 Services

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:

  • CSR: Short for Cloud Services Router. Refers to the Cisco Cloud Services Router 1000v, used in releases prior to release 25.0(3).

  • CCR: Short for Cisco Cloud Router. Refers to the Cisco Catalyst 8000V, used in release 25.0(3) and later.

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.

Table 3. New Features and Changed Behavior in Cisco Cloud APIC for Release 25.0(2)

Feature or Change

Description

Where Documented

Support for site-external EPGs using Azure VPN gateways

Beginning with release 25.0(2), support is available for providing connectivity between a Cloud APIC-managed cloud site and a non-ACI remote site using VPN gateway.

Configuring Connectivity Between Cloud APIC-Managed Cloud Site and Non-ACI Remote Site

Support for configuring routing and security policies independently in Azure and AWS

Beginning with release 25.0(2), the following updates are available for the routing policies:

  • Support for route maps-based route leaking between a pair of internal VRFs

  • Support for the internal VRF route leak policy, which allows you to choose whether you want to use contract-based routing or maps-based routing between a pair of internal VRFs

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 VM scale sets for Azure NLB backend pools

Beginning with release 25.0(2), support is added for Azure virtual machine scale sets as backend targets for load balancers.

Deploying Layer 4 to Layer 7 Services

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.

Changes with overlay-2 (secondary) VRF

Prior to release 25.0(2), the overlay-2 VRF, which is a secondary VRF, was created in the infra tenant implicitly during the Cisco Cloud APIC bringup, and you would have to create services for Azure only in the overlay-2 (secondary) VRF.

Beginning with release 25.0(2), that restriction is removed and the overlay-2 VRF is no longer created implicitly in the infra tenant during the Cisco Cloud APIC bringup.

Understanding Changes With the overlay-2 (Secondary) VRF
Table 4. New Features and Changed Behavior in Cisco Cloud APIC for Release 25.0(1)

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:

  • 4.1(x) (support for AWS only)

  • 4.2(x)

  • 5.0(x)

  • 5.1(x)

  • 5.2(x)

  • 25.0(x)

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).

Monitoring VM Host Metrics

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.

External Network Connectivity

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.

Understanding Supported Routing and Security Policies