Cisco Application Policy Infrastructure Controller Release Notes, Release 5.2(2)

May 6, 2024

In the Miscellaneous Compatibility Information section, added:

November 29, 2022

In the Known Issues section, added:

November 18, 2022

In the Open Issues section, added bug CSCwc66053.

September 27, 2022

In the Open Issues section, added bug CSCwc49449.

August 1, 2022

In the Miscellaneous Compatibility Information section, added:

July 1, 2022

In the Open Issues section, added bug CSCwb93239.

June 30, 2022

In the section Miscellaneous Compatibility, added information about Cisco Nexus Dashboard Insights creating the cisco_SN_NI user.

April 12, 2022

In the Open Issues section, added bug CSCvz94062.

March 21, 2022

In the Miscellaneous Compatibility Information section, added:

February 23, 2022

In the Miscellaneous Compatibility Information section, added:

November 29, 2021

In the Open Issues section, added bug CSCvz98577.

November 16, 2021

In the Known Issues section, added bugs CSCvx78018 and CSCvy07935.

November 2, 2021

In the Miscellaneous Compatibility Information section, added:

October 12, 2021

Release 5.2(2h) became available. Added the resolved bugs for this release.

September 29, 2021

Release 5.2(2g) became available. Added a resolved bug for this release.

August 17, 2021

Release 5.2(2f) became available; there are no changes to this document for this release. See the Cisco Nexus 9000 ACI-Mode Switches Release Notes, Release 15.2(2) for the changes in this release.

August 9, 2021

Removed bug CSCvy44014. The information is documented in the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide, Release 5.2(x). See the "Guidelines and Limitations for Configuring Policy-Based Redirect" section.

July 26, 2021

In the Miscellaneous Compatibility Information section, the CIMC 4.1(3c) release is now recommended for UCS C220/C240 M5 (APIC-L3/M3).

July 9, 2021

Release 5.2(2e) became available.

N/A

There are no new software features in this release.

CSCvz65560

After upgrading the Cisco APIC to a 5.x release, such as 5.2(2f), while the switches are still running a 14.x or earlier release, contract configuration/update/association with the mixed releases can cause the switch zoning rule to become disabled, which results in network disruption.

5.2(2f) and later

CSCvz65560

In a mixed version fabric in which the Cisco APIC is running a 5.x release and the switches are running a 14.x or earlier release, addtion/update/association of a contract with TCP filter that has a port range value of "22" (that is, the port value for SSH), the following incorrect behavior can be encountered:

1. If the TCP port filter is defined as a range of x-22, where x is between 1 and 21, then this mixed mode causes the switch's security policy (zoning rule) to become disabled, which causes network disruption.

2. If the TCP port range is 22-22 (that is, exactly matching port 22), then this mixed mode causes the switch's security policy (zoning rule) to get incorrectly programmed to allow all TCP traffic instead of permitting SSH only.

Upgrading the Cisco APIC to a 5.x release without making the contract configuration changes does not trigger these problems.

5.2(2f)

CSCvy17504

When the OpFlexAgent moved from one vPC pair leaf switches to a new vPC pair, it may take up to 20 minutes for the OpFlexAgent detected the movement, and reconnect the OpFlex channel.  Ideally, this should be completed within a few seconds.

5.2(2e) through 5.2(2g)

CSCvz12372

Endpoints that are shown under an endpoint group created by the OpenStack controller based on the Neutron network configuration are missing information about the Hosting Server as well as the Reporting Controller name.

OpenStack topology information is missing for Nova virtual machines.

5.2(2e) through 5.2(2g)

CSCvg81020

For strict security requirements, customers require custom certificates that have RSA key lengths of 3072 and 4096.

5.2(2e) and later

CSCvm56946

Support for local user (admin) maximum tries and login delay configuration.

5.2(2e) and later

CSCvs97029

All the external prefixes from VRF-A could be leaked to VRF-C even when an inter-VRF ESG leak route is configured for a specific prefix.

5.2(2e) and later

CSCvt99966

A SPAN session with the source type set to "Routed-Outside" goes down. The SPAN configuration is pushed to the anchor or non-anchor nodes, but the interfaces are not pushed due to the following fault: "Failed to configure SPAN with source SpanFL3out due to Source fvIfConn not available".

5.2(2e) and later

CSCvx90225

The browser hangs when clicking on the alert bell in the header bar.

5.2(2e) and later

CSCvy00746

A breakout parent port shows in the drop-down list for the SPAN source even after the port is broken out.

5.2(2e) and later

CSCvy17113

When there are two or more service graph associated contracts between the same pair of consumer and provider EPGs, and each contract is associated to a different Instp (by virtue of service graph configuration), imported/VRF-leaked Instp routes/subnets would not get cleaned up when one of those contracts is deleted from the list of contracts under the EPG. Imported routes /subnets would get cleaned up when the last contract between that EPG pair is deleted. There should be no impact to the traffic forwarding. This issue is about the cleanup of leaked routes.

5.2(2e) and later

CSCvy21881

An upgrade fails due to an incompatible target version. The upgradeStatusStr for maintUpgJob is empty, due to which the GUI is not able to show the correct state.

5.2(2e) and later

CSCvy29992

On the Cisco APIC CLI, the "moconfig commit" command triggers a "No such file or directory" error. The command successfully commits the changes, but the fact that this error shows up results in confusion for the end user.

5.2(2e) and later

CSCvy33994

On the Cisco APIC CLI, using the "moset" command to set an managed object attribute to the same value results in the following error: [Errno 1] Operation not permitted.

5.2(2e) and later

CSCvy40511

Traffic from an endpoint under a remote leaf switch to an external node and its attached external networks is dropped. This occurs if the external node is attached to an L3Out with a vPC and there is a redistribution configuration on the L3Out to advertise the reachability of the external nodes as direct-attached hosts.

5.2(2e) and later

CSCvy85417

The show catalog is empty, which causes all switch discovery to fail because there is no catalog information present.

5.2(2e) and later

CSCvy95710

The following 2 faults are raised in Cisco APIC when Anycast is configured on a Layer 4 to Layer 7 services device and the consumer/provider EPG of this contract is stretched across sites:

"Anycast is enabled in SvcRedirectPol but Consumer/Provider EPg is stretched (Multi-site EPg)"

"Anycast is enabled in LIfCtx but Consumer/Provider EPgs are stretched (Multi-site EPg)"

5.2(2e) and later

CSCvz94062

An SMU's upgrade status shows as "reload pending," but the reload is actually completed and the SMU is activated.

5.2(2e) and later

CSCvz98577

In an OpenShift on OpenStack setup, after VM migration, and connectivity to the pods inside that VM may be lost when accessed from pods running on other VMs not on that same physical host.

5.2(2e) and later

CSCwa58709

The GIPo address is only visible on APIC 1 when using the command "cat /data/data_admin/sam_exported.config". The command output from the other APICs outputs do not show the GIPo address.

5.2(2e) and later

CSCwb93239

The GUI displays the following error:

      Failed, Local Upload Failure Msg (Request failed with status code 413).

5.2(2e) and later

CSCwc49449

When a maintenance policy has multiple switch nodes, such as vPC pair nodes, an SMU's uninstallation gets stuck in the "queued" state for one of the nodes.

5.2(2e) and later

CSCwc66053

Preconfiguration validations for L3Outs that occur whenever a new configuration is pushed to the Cisco APIC might not get triggered.

5.2(2e) and later

CSCwe58398

This is added functionality for upgrade show command.

1. acidiag show postupgrade -service <dme>   -> This gives details for dmes and which shard still have pending postUpgradeCb.

2.acidiag show postupgrade -service <dme> -shard <shard_id> -> This gives the details of log path for the dmes and shard for which postUpgradeCb has been completed.

5.2(2e) and later

CSCwh84052

When using the OpenStack integration, the Cisco APIC VMM Manager process may consume more memory than is available and then end.

5.2(2e) and later

CSCwh98712

When running "show running-config" from API CLI, the command takes several minutes to complete. Several thousand API requests are seen in access.log querying ptpRsProfile on every static path.

5.2(2e) and later

CSCwi01316

In the following topology:

Tenant 1:

VRF 1 > EPG A, EPG B.  There is an any-to-any Intra VRF instance contract and EPG A and B are providers for an inter-VRF instance contract.

VRF 2 > L3Out or EPG. The VRF instance consumes the inter-VRF instance contract.

Traffic will unexpectedly get sent to the wrong rule when inter-VRF instance traffic is flowing.

5.2(2e) and later

CSCwi34095

App installation fails on the Cisco APIC with the error "Unable to add elasticsearch credentials".

This is seen for any app making use of Elasticsearch, such as Nexus Insight Cloud Connector.

5.2(2e) and later

CSCvy17504

When the OpFlexAgent moved from one vPC pair leaf switches to a new vPC pair, it may take up to 20 minutes for the OpFlexAgent detected the movement, and reconnect the OpFlex channel.  Ideally, this should be completed within a few seconds.

5.2(2h)

CSCvz12372

Endpoints that are shown under an endpoint group created by the OpenStack controller based on the Neutron network configuration are missing information about the Hosting Server as well as the Reporting Controller name.

OpenStack topology information is missing for Nova virtual machines.

5.2(2h)

CSCvz17367

The scenario is related to OpenShift nested in OpenStack, where the opflexODev object for OpenShift virtual machines, which were migrated between compute nodes, was pointing to an old compute node from which the virtual machines were migrated.

5.2(2h)

CSCvz65560

In a mixed version fabric in which the Cisco APIC is running a 5.x release and the switches are running a 14.x or earlier release, addtion/update/association of a contract with TCP filter that has a port range value of "22" (that is, the port value for SSH), the following incorrect behavior can be encountered:

1. If the TCP port filter is defined as a range of x-22, where x is between 1 and 21, then this mixed mode causes the switch's security policy (zoning rule) to become disabled, which causes network disruption.

2. If the TCP port range is 22-22 (that is, exactly matching port 22), then this mixed mode causes the switch's security policy (zoning rule) to get incorrectly programmed to allow all TCP traffic instead of permitting SSH only.

Upgrading the Cisco APIC to a 5.x release without making the contract configuration changes does not trigger these problems.

5.2(2g)

CSCvy13772

A standby APIC (in Layer 3 standalone mode) will not automatically upgrade along with the active Cisco APICs.

5.2(2e)

CSCvy46965

In the 5.2(2) release, an app gets stuck installing or there is fault for some containers not running.

5.2(2e)

CSCvj26666

The "show run leaf|spine <nodeId>" command might produce an error for scaled up configurations.

5.2(2e) and later

CSCvj90385

With a uniform distribution of EPs and traffic flows, a fabric module in slot 25 sometimes reports far less than 50% of the traffic compared to the traffic on fabric modules in non-FM25 slots.

5.2(2e) and later

CSCvq39764

When you click Restart for the Microsoft System Center Virtual Machine Manager (SCVMM) agent on a scaled-out setup, the service may stop. You can restart the agent by clicking Start.

5.2(2e) and later

CSCvq58953

One of the following symptoms occurs:

App installation/enable/disable takes a long time and does not complete.

Nomad leadership is lost. The output of the acidiag scheduler logs members command contains the following error:

Error querying node status: Unexpected response code: 500 (rpc error: No cluster leader)

5.2(2e) and later

CSCvr89603

The CRC and stomped CRC error values do not match when seen from the APIC CLI compared to the APIC GUI. This is expected behavior. The GUI values are from the history data, whereas the CLI values are from the current data.

5.2(2e) and later

CSCvs19322

Upgrading Cisco APIC from a 3.x release to a 4.x release causes Smart Licensing to lose its registration. Registering Smart Licensing again will clear the fault.

5.2(2e) and later

CSCvs77929

In the 4.x and later releases, if a firmware policy is created with different name than the maintenance policy, the firmware policy will be deleted and a new firmware policy gets created with the same name, which causes the upgrade process to fail.

5.2(2e) and later

CSCvx75380

svcredirDestmon objects get programmed in all of the leaf switches where the service L3Out is deployed, even though the service node may not be connected to some of the leaf switch.

There is no impact to traffic.

5.2(2e) and later

CSCvx78018

A remote leaf switch has momentary traffic loss for flushed endpoints as the traffic goes through the tglean path and does not directly go through the spine switch proxy path.

5.2(2e) and later

CSCvy07935

xR IP flush for all endpoints under the bridge domain subnets of the EPG being migrated to ESG. This will lead to a temporary traffic loss on remote leaf switch for all EPGs in the bridge domain. Traffic is expected to recover.

5.2(2e) and later

CSCvy34357

Starting with the 5.2(2) release, the following apps built with the following non-compliant Docker versions cannot be installed nor run:

·         ConnectivityCompliance 1.2

·         SevOneAciMonitor 1.0

5.2(2e) and later

CSCvy45358

The file size mentioned in the status managed object for techsupport "dbgexpTechSupStatus" is wrong if the file size is larger than 4GB.

5.2(2e) and later

N/A

If you are upgrading to Cisco APIC release 4.2(6o), 4.2(7l), 5.2(1g), or later, ensure that any VLAN encapsulation blocks that you are explicitly using for leaf switch front panel VLAN programming are set as "external (on the wire)." If these VLAN encapsulation blocks are instead set to "internal," the upgrade causes the front panel port VLAN to be removed, which can result in a datapath outage.

5.2(2e) and later

N/A

Beginning in Cisco APIC release 4.1(1), the IP SLA monitor policy validates the IP SLA port value. Because of the validation, when TCP is configured as the IP SLA type, Cisco APIC no longer accepts an IP SLA port value of 0, which was allowed in previous releases. An IP SLA monitor policy from a previous release that has an IP SLA port value of 0 becomes invalid if the Cisco APIC is upgraded to release 4.1(1) or later. This results in a failure for the configuration import or snapshot rollback.

The workaround is to configure a non-zero IP SLA port value before upgrading the Cisco APIC, and use the snapshot and configuration export that was taken after the IP SLA port change.

5.2(2e) and later

N/A

If you use the REST API to upgrade an app, you must create a new firmware.OSource to be able to download a new app image.

5.2(2e) and later

N/A

In a multipod configuration, before you make any changes to a spine switch, ensure that there is at least one operationally "up" external link that is participating in the multipod topology. Failure to do so could bring down the multipod connectivity. For more information about multipod, see the Cisco Application Centric Infrastructure Fundamentals document and the Cisco APIC Getting Started Guide.

5.2(2e) and later

N/A

With a non-english SCVMM 2012 R2 or SCVMM 2016 setup and where the virtual machine names are specified in non-english characters, if the host is removed and re-added to the host group, the GUID for all the virtual machines under that host changes. Therefore, if a user has created a micro segmentation endpoint group using "VM name" attribute specifying the GUID of respective virtual machine, then that micro segmentation endpoint group will not work if the host (hosting the virtual machines) is removed and re-added to the host group, as the GUID for all the virtual machines would have changed. This does not happen if the virtual name has name specified in all english characters.

5.2(2e) and later

N/A

A query of a configurable policy that does not have a subscription goes to the policy distributor. However, a query of a configurable policy that has a subscription goes to the policy manager. As a result, if the policy propagation from the policy distributor to the policy manager takes a prolonged amount of time, then in such cases the query with the subscription might not return the policy simply because it has not reached policy manager yet.

5.2(2e) and later

N/A

When there are silent hosts across sites, ARP glean messages might not be forwarded to remote sites if a leaf switch without -EX or a later designation in the product ID happens to be in the transit path and the VRF is deployed on that leaf switch, the switch does not forward the ARP glean packet back into the fabric to reach the remote site. This issue is specific to transit leaf switches without -EX or a later designation in the product ID and does not affect leaf switches that have -EX or a later designation in the product ID. This issue breaks the capability of discovering silent hosts.

5.2(2e) and later

N/A

Typically, faults are generally raised based on the presence of the BGP route target profile under the VRF table. However, if a BGP route target profile is configured without actual route targets (that is, the profile has empty policies), a fault will not be raised in this situation.

5.2(2e) and later

N/A

MPLS interface statistics shown in a switch's CLI get cleared after an admin or operational down event.

5.2(2e) and later

N/A

MPLS interface statistics in a switch's CLI are reported every 10 seconds. If, for example, an interface goes down 3 seconds after the collection of the statistics, the CLI reports only 3 seconds of the statistics and clears all of the other statistics.

5.2(2e) and later

Microsoft Hyper-V

N/A

VMM Integration and VMware Distributed Virtual Switch (DVS)

6.5, 6.7, and 7.0

Cisco ACI Virtualization Guide, Release 5.2(x)

APIC-L1

Cisco APIC with large CPU, hard drive, and memory configurations (more than 1000 edge ports)

APIC-L2

Cisco APIC with large CPU, hard drive, and memory configurations (more than 1000 edge ports)

APIC-L3

Cisco APIC with large CPU, hard drive, and memory configurations (more than 1200 edge ports)

APIC-M1

Cisco APIC with medium-size CPU, hard drive, and memory configurations (up to 1000 edge ports)

APIC-M2

Cisco APIC with medium-size CPU, hard drive, and memory configurations (up to 1000 edge ports)

APIC-M3

Cisco APIC with medium-size CPU, hard drive, and memory configurations (up to 1200 edge ports)

Cisco UCS M4-based Cisco APIC

The Cisco UCS M4-based Cisco APIC and previous versions support only the 10G interface. Connecting the Cisco APIC to the Cisco ACI fabric requires a same speed interface on the Cisco ACI leaf switch. You cannot connect the Cisco APIC directly to the Cisco N9332PQ ACI leaf switch, unless you use a 40G to 10G converter (part number CVR-QSFP-SFP10G), in which case the port on the Cisco N9332PQ switch auto-negotiates to 10G without requiring any manual configuration.

Cisco UCS M5-based Cisco APIC

The Cisco UCS M5-based Cisco APIC supports dual speed 10G and 25G interfaces. Connecting the Cisco APIC to the Cisco ACI fabric requires a same speed interface on the Cisco ACI leaf switch. You cannot connect the Cisco APIC directly to the Cisco N9332PQ ACI leaf switch, unless you use a 40G to 10G converter (part number CVR-QSFP-SFP10G), in which case the port on the Cisco N9332PQ switch auto-negotiates to 10G without requiring any manual configuration.

N2348UPQ

To connect the N2348UPQ to Cisco ACI leaf switches, the following options are available:

Directly connect the 40G FEX ports on the N2348UPQ to the 40G switch ports on the Cisco ACI leaf switches

Break out the 40G FEX ports on the N2348UPQ to 4x10G ports and connect to the 10G ports on all other Cisco ACI leaf switches.

Note: A fabric uplink port cannot be used as a FEX fabric port.

N9K-C9348GC-FXP

This switch does not read SPROM information if the PSU is in a shut state. You might see an empty string in the Cisco APIC output.

N9K-C9364C-FX

Ports 49-64 do not supporFut 1G SFPs with QSA.

N9K-C9508-FM-E

The Cisco N9K-C9508-FM-E2 and N9K-C9508-FM-E fabric modules in the mixed mode configuration are not supported on the same spine switch.

N9K-C9508-FM-E2

The Cisco N9K-C9508-FM-E2 and N9K-C9508-FM-E fabric modules in the mixed mode configuration are not supported on the same spine switch.

The locator LED enable/disable feature is supported in the GUI and not supported in the Cisco ACI NX-OS switch CLI.

N9K-C9508-FM-E2

This fabric module must be physically removed before downgrading to releases earlier than Cisco APIC 3.0(1).

N9K-X9736C-FX

The locator LED enable/disable feature is supported in the GUI and not supported in the Cisco ACI NX-OS Switch CLI.

N9K-X9736C-FX

Ports 29 to 36 do not support 1G SFPs with QSA.

Cisco NX-OS

15.2(2)

Cisco UCS Manager

2.2(1c) or later is required for the Cisco UCS Fabric Interconnect and other components, including the BIOS, CIMC, and the adapter.

CIMC HUU ISO

Network Insights Base, Network Insights Advisor, and Network Insights for Resources

For the release information, documentation, and download links, see the Cisco Network Insights for Data Center page.

For the supported releases, see the Cisco Data Center Networking Applications Compatibility Matrix.

Cisco Nexus 9000 ACI-Mode Switches Release Notes, Release 15.2(2)

The release notes for Cisco NX-OS for Cisco Nexus 9000 Series ACI-Mode Switches.

Verified Scalability Guide for Cisco APIC, Release 5.2(1) and Cisco Nexus 9000 Series ACI-Mode Switches, Release 15.2(1)

This guide contains the maximum verified scalability limits for Cisco Application Centric Infrastructure (ACI) parameters for Cisco APIC and Cisco Nexus 9000 Series ACI-Mode Switches.

Note: The 5.2(1) release document applies to the 5.2(2) release.