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 Network (Azure) Load Balancer. |
You can deploy a Layer 4 device that distributes the in-bound flow packets to the back-end pool targets. |
|
|
Support for Inter-VNET service graphs. |
You can deploy a Provider EPG and Service devices in same VPC/VNET. |
|
|
Support for Multi-node service Graph |
You can enable multiple deployment scenarios with service graphs. |
|
|
Support for multiple CIDR and subnet blocks on the infra VNet. |
You can configure multiple CIDR and subnet blocks on the infra VNet. |
|
|
Support for cloud EPGs and cloud external EPGs in the infra tenant. |
You can create cloud EPGs and cloud external EPGs in the infra tenant, where all the cloud EPGs and cloud external EPGs will be associated with the overlay-2 VRF in the infra tenant. |
|
|
Support for Layer 4 to Layer 7 service redirect |
Support is now available for Layer 4 to Layer 7 service redirect. |
|
|
Tag-based search |
While viewing the cloud resource details for Endpoints, search based on cloud tag attribute is supported. |
|
|
Naming convention support for more than 32 characters for the tenant and VRF name combination |
All VRFs are assigned a VrfEncoded value. If the tenant and VRF name combination has more than 32 characters, then a VRF name (which also contains the tenant name) is identified in the cloud router using the VrfEncoded value. |
|
|
Support for comma-separated filters for rule creation in contracts |
After a contract is created, some of the rules defined in the contract can be consolidated based on certain criteria. |
|
|
Support for a static IP address for a load balancer |
While creating a device, you can assign a static IP address for an application load balancer (ALB) or a network load balancer (NLB). |
|
|
Configuration drifts information |
Cloud APIC provides visibility into any security policy (contract) configuration discrepancy between what you deploy from the Cloud APIC and what is actually configured in the cloud site. |
|
|
Custom naming rules for cloud resources |
You can create a global naming policy on the Cloud APIC, which allows you to define a custom cloud resources naming convention for all objects deployed from the Cloud APIC into the Azure cloud. |
|
Feature or Change |
Description |
Where Documented |
|---|---|---|
|
Additional error codes |
Additional error codes have been added as part of Release 5.0(1) |
Feedback