Cisco Releases Next Version of ACI APIC

Yesterday Cisco released the newest version of the NX-OS and ACI APIC software

Bug ID


Some events on bootup are missed on leaf or spine switches.


In some of the 5-minute statistics data the count of ten-second samples is 29 instead of 30.


The DSCP value specified on an external endpoint group does not take effect on filter rules on the leaf switch.


Users can change their password any number of times.The password change restriction policies are not obeyed.


Host name resolution of the syslog server fails on leaf and spine switches over inband connectivity.


Configuration modifications to the ERSPAN destination parameters (dst IP/TTL/flow id etc) do not take effect on the physical and virtual leaf switches.


A user with read-only access can initiate a L4-L7 device package download.


In the tracerouteExecTn managed object, the source node ID field contains only one of the two nodes when the source is behind a vPC.


The download of an image into the repository fails if you have any special characters in your password.


A fault for a switch firmware upgrade failure does not appear under the Firmware Groups tab.


An APIC process is busy when a scheduled export configuration is spawned every hour.


When shutting down a port channel that is a member of a vPC, the entire vPC will shut down.


The techsupport remote command displays an exception when trying to collect the techsupport on the CLI.


After the same tag is configured for two interfaces, a new tag cannot be added or an existing tag associated with a third interface.


Queries to the fault/health/audit records stored on an APIC that occur at the same time as fault records are written to the database cause database corruption.


A graph instance gets stuck in the applying state but no faults appear at the tenant level in the GUI.


Modifying or deleting endpoint group configuration parameters can cause the corresponding Graph Instance to go into a “missing config-params” fault state.


Importing firmware policies that are stale affects fabric discovery.


In vCenter 5.5 deployments, auto-placement of a VNIC can cause the MAC address to disappear.


Users can configure an endpoint to “any” or “any” to an endpoint flow-based atomic counter rule, which is not supported.


If a vShield controller is configured and operational in a version earlier than 1.0(2j), a policy based upgrade to 1.0(2j), or subsequent release, will fail in a vShield configuration. Also, a vShield configuration exported from an APIC version earlier than 1.0(2j) cannot be imported back in the APIC running software version 1.0(2j) or later.

Leave a Comment

Your email address will not be published.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Scroll to Top