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

December 4, 2024

Release 5.3(2e) became available. Added the resolved bug(s) for this release.

October 7, 2024

In the Miscellaneous Compatibility Information section, updated the CIMC versions:  

September 27, 2024

Release 5.3(2d) became available. Added the resolved bugs for this release.

June 27, 2024

Release 5.3(2c) became available. Added the resolved bugs for this release.

May 1, 2024

In the Miscellaneous Compatibility Information section, added:

April 2, 2024

Release 5.3(2b) became available. Added the resolved bugs for this release.

February 1, 2024

Release 5.3(2a) became available.

N/A

N/A

There are no new software features in this release.

CSCwj42027

F1527, F1528 faults raised for /var/log/dme/log crossing 75% usage and cleared over and over.

5.3(2a) through 5.3(2d)

CSCvg81020

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

5.3(2a) and later

CSCvm56946

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

5.3(2a) 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.3(2a) 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.3(2a) and later

CSCvz72941

While performing ID recovery, id-import gets timed out. Due to this, ID recovery fails.

5.3(2a) and later

CSCvz83636

For a health record query using the last page and a time range, the GUI displays some health records with a creation time that is beyond the time range (such as 24h).

5.3(2a) 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.3(2a) and later

CSCwa90058

When a VRF-level subnet <fvRtSummSubnet> and instP-level subnet <l3extSubnet> with a summary policy is configured for an overlapping subnet, the routes will get summarized by the configuration that was added first. But, the fault on the configuration that was added last will not be shown in the Cisco APIC GUI.

5.3(2a) and later

CSCwa90084

- Traffic disruption across a vPC pair on a given encapsulation.

OR

- EPG flood in encap blackholing on a given encapsulation.

OR

- STP packets received on an encapsulation on a given port are not forwarded on all the leaf switches where the same EPG/same encapsulation is deployed.

5.3(2a) and later

CSCwb69095

Failover can no longer be performed on a specific node.

5.3(2a) and later

CSCwd26277

When deploying a service graph, the dialog does not list all bridge domains for the provider connector. This issue is observed when you enter or edit the bridge domain name in the consumer connector field. After this, the provider connector will only list the bridge domain that is selected by the consumer connector field.

5.3(2a) and later

CSCwd26277

When deploying a service graph, the dialog does not list all bridge domains for the provider connector. This issue is observed when you enter or edit the bridge domain name in the consumer connector field. After this, the provider connector will only list the bridge domain that is selected by the consumer connector field.

5.3(2a) and later

CSCwe39988

The Cisco APIC GUI becomes unresponsive when there is large configuration for given tenant and VRF instance.

5.3(2a) 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.3(2a) and later

CSCwe92155

After configuring syslog using TCP on port 59500, the logit was sent out normally and netstat showed that it was established. However, after aborting the connection from the syslog server side, the TCP connection went from ESTABLISHED to CLOSE_WAIT and disappeared from the APIC side.

5.3(2a) and later

CSCwf55317

1.     Go to Tenant > Application Profile > Topology.

2.     Drag and drop a contract. Problem 1: No pop up displays.

Drag and drop an EPG icon, then cancel the create view. Problem 2: The pop up remains open.

5.3(2a) and later

­­­CSCwf59938

Fault code F1414 is triggered and cleared manually. After certain time, the fault is triggered again. This issue occurs when using the syslog server FQDN.

5.3(2a) and later

CSCwf92856

During upgrade "deserialization error" is seen on APIC 1 PD.

5.3(2a) and later

CSCwh05135

Override vpc interface policy doesnot consistently take precedence over regular vpc interface policy.Upon a leaf reload, its quite random which policy takes precedence, and accordingly the vlans get programmed.If the override or regular AEP is missing the relevant domain association/vlans, then those vlans are not programmed causing outages.

5.3(2a) and later

CSCwh07037

An outage occurred because traffic coming from the TEPs was dropped by the receiving leaf switches with INFRA_ENCAP_SRC_TEP_MISS.

5.3(2a) and later

CSCwh08862

In a configuration that has IPv4 diabled, the replace operation performed from the GUI fails.

5.3(2a) and later

CSCwh17898

The "panic: runtime error: invalid memory address or nil pointer dereference." Error occurred and then F1419 (Service kron failed on apic) was raised.

5.3(2a) and later

CSCwh18649

Inter-pod/Inter-site BGP peer is incorrectly marked as "manual,wan" under the BGP for the peer managed object of a spine switch.

5.3(2a) and later

CSCwh28834

The "show running config" command does not work in the APIC CLI and generates the following errors:

Error while processing mode: interface

Error while processing mode: leaf

Error while processing mode: configure

Error: ERROR occurred: <class 'xml.etree.ElementTree.ParseError'>, not well-formed (invalid token): line 1, column 51242,   File "/mgmt/opt/controller/yaci/yaci/_cfg.py", line 18, in _execute_func

    subCmd.runningConfig(ctx, **kwargs)

5.3(2a) and later

CSCwh41632

Enhancement - show apic upgrade complete only after postUpgradeCb is done

5.3(2a) and later

CSCwh41865

When upgrading an APIC, the "from" version is displayed as "to" version in the event record.

5.3(2a) and later

CSCwh44987

When a non-default OOB management EPG is configured and a default one is removed from the configuration, the default EPG will be recreated automatically after a fabric upgrade. This is causes fault F0523 "Configuration failed for EPG default due to Not Associated With Management Zone".

5.3(2a) and later

CSCwh53706

In scale setups, when there are more than the usual number of objects and if the user tries to load the Capacity Dashboard page, the page times out. A few queries that are hit from the browser and the page become stuck for few seconds.

5.3(2a) and later

CSCwh53727

The API call /mqapi2/deployment.query.json?mode=getvmmCapInfo that is done against the Cisco APICs by an external management system takes too long to process.

5.3(2a) and later

CSCwh56716

When the Cisco APICs use Direct Connect to CSSM, running the "show license usage" command on APIC 1, 2, or 3 shows ACI_LEAF_ESS_10G 6 in use. When APICs 2 and 3 are restarted, this output is unchanged. When APIC 1 is restarted, the output becomes "No Licenses in use" on APICs 1, 2, and 3. The "Registering for Smart Licensing with Direct Connect to CSSM Using the GUI" process has to be done again.This was tested in the lab with Cisco APIC releases 5.2(6g), 5.2(7g), and 6.0(2j)

5.3(2a) and later

CSCwh67428

The GUI does not display maxSpeed and direction information in the equipment view.

5.3(2a) and later

CSCwh74484

ACI pushes the VLANs from the old VLAN pool after changing the vNIC template in the UCSM

5.3(2a) and later

CSCwh75348

Decommission an APIC causes the message "the node configuration will be wiped out from controller" to display even though the controllers still retain the user configuration.

5.3(2a) and later

CSCwh78409

The SNMPD service failed on all Cisco APICs after configuring SNMPv3.

5.3(2a) and later

CSCwh81272

The system resets due to a policyelem high availability policy reset.

5.3(2a) and later

CSCwh83273

A Cisco APIC cannot be added to the cluster because the GUI rejects the ID if is not within the range of 1-7.The Initial Setup Configuration states that the fabric ID valid range is 1-128.

5.3(2a) and later

CSCwh87245

An edmManagedNic or compManagedNic object may be mapped to the wrong server (compHv).

5.3(2a) and later

CSCwh87458

Search Filters in Endpoint - Operational - Client Endpoints do not show up in the endpoint learning filter.

5.3(2a) and later

CSCwh95573

Fault "F4142" is raised when there is inconsistency in FNV and the idmgr database. Even though the addrAssigner in FNV is set to 0 and the corresponding "identContextElement" managed object is missing from the idmgr database, the fault gets raised.

5.3(2a) 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.3(2a) 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.3(2a) and later

CSCwi03663

Recent upgraded versions of SCP servers do not support some of the old ciphers or host key algorithms causing SCP to/from APIC to break.

5.3(2a) and later

CSCwi06427

Navigating to FABRIC -> Inventory -> Pod1 -> Operational -> Routes -> IPv6 learned routes results in the following error message:Value is not specified for the argument 'undefined'

5.3(2a) and later

CSCwi09894

In a mini ACI fabric, the physical APIC does not join the cluster after power cycling the entire setup.

5.3(2a) and later

CSCwi24859

In the Cisco APIC GUI, the Security tab might not work.

5.3(2a) and later

CSCwi40671

In a remote leaf switch, when the initial policy download happens, nginx generates a core. The process recovers by itself after a restart. This issue does not have any major functionality impact.

5.3(2a) and later

CSCwi52324

The fault F3227 "ACI failed processing an already accepted configuration change" continuously gets raised

5.3(2a) and later

CSCwj08117

After a reboot is triggered, any of the Cisco APICs take around 1 hour to reach the cluster fully fit status and the affected DME is ifc_observer. During the issue, there is non-optimal leader for some shards for the service ifc_observer, which it clears after 30 minutes.

5.3(2a) and later

CSCwj13396

ACI switches show in maintenance with the CLI command "acidiag fnvread" on Cisco APIC, but they show "normal" in vsh and even top. System also shows In service.

- Switches do not show up in the GUI nor API for configurations, as APIC vectors it as in maintenance. This severely impacts the ability to make changes.

- Switches may continue to work normally even though no new configurations can be made on them.

5.3(2a) through 5.3(2c)

CSCwj17966

The Cisco APIC bootmgr or appliance director allows an incorrect attribute/value update to be received in LLDP TLV due to miscabling.

5.3(2a) and later

CSCwj23752

Changing in the name of the remote-destination group stops the sending of syslog messages to the remote destination. Changing the port number or forwarding facility does not affect the sending of the messages. Only when the name is changed does the leaf switch stop sending the syslog messages. Enabling and disabling the policy does not resume the sending of the messages.

5.3(2a) and later

CSCwj38953

log_bin_decode crashes on distinguished name decoding failures.

5.3(2a) and later

CSCwj55258

Fault F4144 will not clear from the Cisco APIC even with matching dhcpPool and Fabric Node Vector information.

5.3(2a) and later

CSCwj57993

The F0413 PSU fault is not reported by SMART callhome. The tcpdump command on the leaf switch does not show SMTP messages being sent for this fault for which the PSU was removed.

5.3(2a) and later

CSCwj69046

SAML authentication fails when using the HTTPS Proxy 5.2 image.

5.3(2a) and later

CSCwk13546

There are stale hvExtPl objects due to the hvsExtPol managed object not being cleaned up when an EPG is deleted.

Fault F1606 is raised, but has no operational impact:

 desc :Fault delegate: Operational issues detected on portgroup error: Cannot find an EPG policy in the domain for the port group.

5.3(2a) and later

CSCwd54816

Transactions gets stuck in shard due to back-back config import.

5.3(2a) through 5.3(2c)

CSCwh05135

Override vPC interface policy doesnot consistently take precedence over regular vPC interface policy.Upon a leaf reload, its quite random which policy takes precedence, and accordingly the VLANs get programmed. If the override or regular AEP is missing the relevant domain association/VLANs, then those VLANs are not programmed causing outages.

5.3(2a) through 5.3(2c)

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.3(2a) through 5.3(2c)

CSCwi26092

Starting from a Cisco ACI fabric running release 4.2(7w) or earlier with UCSM integration configured and functional, upgrading to a release after 5.2 and re-enabling the UCSM integration application triggers the inventory sync and the VLANs that were programmed are removed.

5.3(2a) through 5.3(2c)

CSCwi60527

LAG uplinks on VC port-groups can get modified to individual uplinks.

5.3(2a) through 5.3(2c)

CSCwj71324

F3083 is not generated for two endpoints in the same EPG having the same IP address.

5.3(2a) through 5.3(2c)

CSCwk61319

APIC : Bootstrap crash both IPv6 enabled and without OOB IPv6 subnet mask in sam.config like below when upgrade/downgrade to 5.3.

5.3(2b), 5.3(2c)

CSCwk15849

The leaf crashed in continue due out of memory. ptplc_sdk invoked oom-killer opflexp dme crashed as well due to out-of-memory.

5.3(2c)

CSCwe93045

There is general slowness when an application contacts the Cisco APIC cluster through the REST API. The same slowness is experienced when accessing using the Cisco APIC GUI.

5.3(2a) and 5.3(2b)

CSCwf04318

In a Cisco APIC 5.2 release, a user in a restricted security domain is allowed to create a VRF instance, but that same restricted mode user is not allowed to delete that VRF instance.

5.3(2a) and 5.3(2b)

CSCwh84052

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

5.3(2a) and 5.3(2b)

CSCwi66348

A Cisco ACI switch can spend hours to complete the bootstrap process. At the worst, the expected completion time should be about 90 minutes.

5.3(2a) and 5.3(2b)

CSCwi71834

Interface Configuration Migration created unexpected infra/access node profile and interface profile for a fabric port. The unexpected infra profile causes a fault.

5.3(2a) and 5.3(2b)

CSCwi78474

An upgraded Cisco APIC may attempt the second upgrade to same version and assume itself as APIC 1, which can cause all Cisco APICs to stop the postUpgradeCb process, which stops the upgrade.

5.3(2a) and 5.3(2b)

CSCwi83667

The Interface Configuration Migration created Leaf profile and interface profile Access with the Spine interface

5.3(2a) and 5.3(2b)

CSCwi97842

After upgrading, the Cisco APIC cluster is diverged and policymgr is down and repeatedly crashing on one Cisco APIC.

5.3(2a) and 5.3(2b)

CSCwi99378

There are packet drops between pods.

5.3(2a) and 5.3(2b)

CSCwj30879

A user can only see the tenant and access policies assigned to nodes. This user can also configure an application profile in the tenant with "create application profile", but cannot see the application profile after configuring it.

5.3(2a) and 5.3(2b)

CSCwj42913

REST API can be used to configure static ports for nodes that are restricted in by a node rule.

5.3(2a) and 5.3(2b)

CSCwj43407

Altering the IP SLA policy for an IP SLA track member led to the crashing of switches.

5.3(2a) and 5.3(2b)

CSCwf20254

There is a delay in downloading and programming of policies on the node.

5.3(2a)

CSCwf92312

Whenever the 'server monitoring' feature is enabled on Cisco APIC and there is a complex password that includes more than one special character, all the RADIUS users that have access to the APICs cannot log in. Users receive the following error: 'Failed to populate authentication data snapshot - AAA Servers are unreachable'. Fault F0021 is raised on all Cisco APICs of the cluster, which says that 'the RADIUS provider is not reachable anymore'.

5.3(2a)

CSCwh36670

During an upgrade, at times it is not known if a DME has completed all the necessary steps to run in the new version. To assess reliably that information, it must be known for which DME and for which managed object the postUpgrade and postClusterUpgrade phases has been executed.

5.3(2a)

CSCwi12992

After upgrade to ACI 5.2(8), the custom SSL certificate is not installed in the Cisco APICs and the default self-signed SSL certificate is used instead.

5.3(2a)

CSCwi40019

The description of an interface is configured but not pushed to a spine switch.

5.3(2a)

CSCwj42027

F1527, F1528 faults raised for /var/log/dme/log crossing 75% usage and cleared over and over.

5.3(2e)

CSCwd54816

Transactions gets stuck in shard due to back-back config import.

5.3(2d)

CSCwh05135

Override vPC interface policy doesnot consistently take precedence over regular vPC interface policy.Upon a leaf reload, its quite random which policy takes precedence, and accordingly the VLANs get programmed. If the override or regular AEP is missing the relevant domain association/VLANs, then those VLANs are not programmed causing outages.

5.3(2d)

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.3(2d)

CSCwi26092

Starting from a Cisco ACI fabric running release 4.2(7w) or earlier with UCSM integration configured and functional, upgrading to a release after 5.2 and re-enabling the UCSM integration application triggers the inventory sync and the VLANs that were programmed are removed.

5.3(2d)

CSCwi60527

LAG uplinks on VC port-groups can get modified to individual uplinks.

5.3(2d)

CSCwj71324

F3083 is not generated for two endpoints in the same EPG having the same IP address.

5.3(2d)

CSCwj13396

ACI switches show in maintenance with the CLI command "acidiag fnvread" on Cisco APIC, but they show "normal" in vsh and even top. System also shows In service.

- Switches do not show up in the GUI nor API for configurations, as APIC vectors it as in maintenance. This severely impacts the ability to make changes.

- Switches may continue to work normally even though no new configurations can be made on them.

5.3(2d)

CSCwk15849

The leaf crashed in continue due out of memory. ptplc_sdk invoked oom-killer opflexp dme crashed as well due to out-of-memory.

5.3(2d)

CSCwk61319

APIC : Bootstrap crash both IPv6 enabled and without OOB IPv6 subnet mask in sam.config like below when upgrade/downgrade to 5.3.

5.3(2d)

CSCwe93045

There is general slowness when an application contacts the Cisco APIC cluster through the REST API. The same slowness is experienced when accessing using the Cisco APIC GUI.

5.3(2c)

CSCwf04318

In a Cisco APIC 5.2 release, a user in a restricted security domain is allowed to create a VRF instance, but that same restricted mode user is not allowed to delete that VRF instance.

5.3(2c)

CSCwh84052

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

5.3(2c)

CSCwi66348

A Cisco ACI switch can spend hours to complete the bootstrap process. At the worst, the expected completion time should be about 90 minutes.

5.3(2c)

CSCwi71834

Interface Configuration Migration created unexpected infra/access node profile and interface profile for a fabric port. The unexpected infra profile causes a fault.

5.3(2c)

CSCwi78474

An upgraded Cisco APIC may attempt the second upgrade to same version and assume itself as APIC 1, which can cause all Cisco APICs to stop the postUpgradeCb process, which stops the upgrade.

5.3(2c)

CSCwi83667

The Interface Configuration Migration created Leaf profile and interface profile Access with the Spine interface

5.3(2c)

CSCwi97842

After upgrading, the Cisco APIC cluster is diverged and policymgr is down and repeatedly crashing on one Cisco APIC.

5.3(2c)

CSCwi99378

There are packet drops between pods.

5.3(2c)

CSCwj30879

A user can only see the tenant and access policies assigned to nodes. This user can also configure an application profile in the tenant with "create application profile", but cannot see the application profile after configuring it.

5.3(2c)

CSCwj42913

REST API can be used to configure static ports for nodes that are restricted in by a node rule.

5.3(2c)

CSCwj43407

Altering the IP SLA policy for an IP SLA track member led to the crashing of switches.

5.3(2c)

CSCwf20254

There is a delay in downloading and programming of policies on the node.

5.3(2b)

CSCwf92312

Whenever the 'server monitoring' feature is enabled on Cisco APIC and there is a complex password that includes more than one special character, all the RADIUS users that have access to the APICs cannot log in. Users receive the following error: 'Failed to populate authentication data snapshot - AAA Servers are unreachable'. Fault F0021 is raised on all Cisco APICs of the cluster, which says that 'the RADIUS provider is not reachable anymore'.

5.3(2b)

CSCwh36670

During an upgrade, at times it is not known if a DME has completed all the necessary steps to run in the new version. To assess reliably that information, it must be known for which DME and for which managed object the postUpgrade and postClusterUpgrade phases has been executed.

5.3(2b)

CSCwi12992

After upgrading to ACI 5.2(8), the custom SSL certificate is not installed in the Cisco APICs and the default self-signed SSL certificate is used instead.

5.3(2b)

CSCwi40019

The description of an interface is configured but not pushed to a spine switch.

5.3(2b)

CSCwf54771

User configuration is missing on APICs and switches following an ungraceful reload or power outage.

5.3(2a)

CSCwh77285

OpFlex OOM crashes in leaf switches.

5.3(2a)

CSCuu11416

An endpoint-to-endpoint ACI policy that uses Layer 2 traffic with an IPv6 header does not get counted within or across ESGs/EPGs.

5.3(2a) and later

CSCvj26666

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

5.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) and later

CSCvs19322

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

5.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) and later

CSCvy10946

With the floating L3Out multipath recursive feature, if a static route with multipath is configured, not all paths are installed at the non-border leaf switch/non-anchor nodes.

5.3(2a) and later

CSCvy34357

Starting with the 5.3(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.3(2a) 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.3(2a) and later

CSCvz06118

In the "Visibility and Troubleshooting Wizard," ERSPAN support for IPv6 traffic is not available.

5.3(2a) and later

CSCvz84444

While navigating to the last records in the various History sub tabs, it is possible to not see any results. The first, previous, next, and last buttons will then stop working too.

5.3(2a) and later

CSCvz85579

VMMmgr process experiences a very high load for an extended period of time that impacts other operations that involve it.

The process may consume excessive amount of memory and get aborted. This can be confirmed with the command "dmesg -T | grep oom_reaper" if messages such as the following are reported:

         oom_reaper: reaped process 5578 (svc_ifc_vmmmgr.)

5.3(2a) and later

CSCwa78573

When the "BGP" branch is expanded in the Fabric > Inventory > POD 1 > Leaf > Protocols > BGP navigation path, the GUI freezes and you cannot navigate to any other page.

This occurs because the APIC gets large set of data in response, which cannot be handled by the browser for parts of the GUI that do not have the pagination.

5.3(2a) and later

CSCwd45200

Hosting server details for AVE endpoints at the operational tab under the EPG is not updated after VM migration.

5.3(2a) and later

CSCwd51537

After changing a VM's name, the name does not get updated for endpoints in the Operational tab of an EPG.

5.3(2a) and later

CSCwk21572

License manager occasionally cores after image upgrade.

5.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) 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.3(2a) and later

N/A

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

5.3(2a) 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.3(2a) and later

Microsoft Hyper-V

N/A

VMM Integration and VMware Distributed Virtual Switch (DVS)

6.5, 6.7, 7.0, and 8.0

Cisco ACI Virtualization Guide, Release 5.3(x)

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-L4

Cisco APIC with large CPU, hard drive, and memory configurations (more than 1200 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)

APIC-M4

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.

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.

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 support 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.3(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.3(2)

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

Verified Scalability Guide for Cisco APIC, Releases 5.2(8) and 5.3(2) and Cisco Nexus 9000 Series ACI-Mode Switches, Releases 15.2(8) and 15.3(2)

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.