Cisco Application Policy Infrastructure Controller Release Notes, Release 3.2(9)

May 1, 2024

In the Miscellaneous Compatibility Information section, removed the older CIMC releases to reduce the clutter.

December 9, 2022

In the Open Bugs section, added bug CSCvw33061.

August 1, 2022

In the Miscellaneous Compatibility Information section, added:

■        4.2(2a) CIMC HUU ISO (recommended) for UCS C220/C240 M5 (APIC-L3/M3)

■        4.1(2k) CIMC HUU ISO (recommended) for UCS C220/C240 M4 (APIC-L2/M2)

March 21, 2022

In the Miscellaneous Compatibility Information section, added:

■        4.1(3f) CIMC HUU ISO (recommended) for UCS C220/C240 M5 (APIC-L3/M3)

February 23, 2022

In the Miscellaneous Compatibility Information section, added:

■        4.1(2g) CIMC HUU ISO (recommended) for UCS C220/C240 M4 (APIC-L2/M2)

November 2, 2021

In the Miscellaneous Compatibility Information section, added:

■        4.1(3d) CIMC HUU ISO (recommended) for UCS C220/C240 M5 (APIC-L3/M3)

August 4, 2021

In the Open Issues section, added bug CSCvy30453.

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

March 11, 2021

In the Miscellaneous Compatibility Information section, for CIMC HUU ISO, added:

■        4.1(3b) CIMC HUU ISO (recommended) for UCS C220/C240 M5 (APIC-L3/M3)

Changed:

■        4.1(2b) CIMC HUU ISO (recommended) for UCS C220/C240 M4 (APIC-L2/M2) and M5 (APIC-L3/M3)

To:

■        4.1(2b) CIMC HUU ISO (recommended) for UCS C220/C240 M4 (APIC-L2/M2

February 9, 2021

In the Open Bugs section, added bug CSCvt07565.

February 5, 2021

Moved bug CSCvr51121 from the open bugs table to the resolved bugs table.

Removed bug CSCvr92532 from the open bugs table. This bug was erroneously included.

February 3, 2021

In the Miscellaneous Compatibility Information section, for CIMC HUU ISO, added:

■        4.1(2b) CIMC HUU ISO (recommended) for UCS C220/C240 M4 (APIC-L2/M2) and M5 (APIC-L3/M3)

December 16, 2020

In the Miscellaneous Compatibility Information section, CIMC release 4.1(1g) is now recommended for UCS C220/C240 M4 (APIC-L2/M2) and UCS C220/C240 M5 (APIC-L3/M3).

April 24, 2020

Release 3.2(9h) became available. There are no changes to this document for this release. See the Cisco NX-OS Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches, Release 13.2(9) for the changes in this release.

March 11, 2020

Release 3.2(9f) became available. Added the resolved bugs for this release. In the New Software Features section, added the link level policies feature.

March 6, 2020

In the Miscellaneous Compatibility Information section, updated the CIMC HUU ISO information for the 4.0(2g) and 4.0(4e) CIMC releases.

November 5, 2019

In the Miscellaneous Compatibility Information, added the supported CIMC versions for APIC-L3/M3.

November 3, 2019

Release 3.2(9b) became available.

Cisco APIC support for the Cisco Network Insights Base Application

Cisco APIC now supports the Cisco Network Insights Base Application release 1.0.1.

See the Cisco Network Insights Base Application for the Cisco Application Policy Infrastructure Controller Release Notes, Release 1.0.1.

N/A

Link level policies

You can now create link level policies under fabric policies. A link level policy applies to the fabric interfaces (leaf switch uplink ports and spine switch ports) at the link level and is used where there might be link noise or transient flaps. In the policy, you configure a link debounce interval. When there is a flap, the fabric interfaces will wait for the debounce interval to pass, then check the link status again to re-confirm the event. If the link is okay at this time, then the interfaces will remain up. The default debounce interval is 0 ms. We recommend a value of 100 ms, but you should choose a value that is appropriate to your fabric.

This feature was added in release 3.2(9f).

N/A

CSCvy30453

For a Cisco ACI fabric that is configured with fabricId=1, if APIC3 is replaced from scratch with an incorrect fabricId of "2," APIC3's DHCPd will set the nodeRole property to "0" (unsupported) for all dhcpClient managed objects. This will be propagated to the appliance director process for all of the Cisco APICs. The process then stops sending the AV/FNV update for any unknown switch types (switches that are not spine nor leaf switches). In this scenario, commissioning/decommissioning of the Cisco APICs will not be propagated to the switches, which causes new Cisco APICs to be blocked out of the fabric.
Another symptom is that the "acidag fnvread" command's output has a value of "unknown" in the role column.

3.2(9h) and later

CSCvs81881

The Cisco APIC PSU voltage and amperage values are zero.

3.2(9f) and later

CSCvt87506

SSD lifetime can be exhausted prematurely if unused Standby slot exists

3.2(9f) and later

CSCvt93482

The per feature container for techsupport "objectstore_debug_info" fails to collect on spines due to invalid filepath.

Given filepath: more /debug/leaf/nginx/objstore*/mo | cat

Correct filepath: more /debug/spine/nginx/objstore*/mo | cat

TAC uses this file/data to collect information about excessive DME writes.

3.2(9f) and later

CSCvu12092

AVE is not getting the VTEP IP address from the Cisco APIC. The logs show a "pending pool" and "no free leases".

3.2(9f) and later

CSCvu49644

A tunnel endpoint doesn't receive a DHCP lease. This occurs with a newly deployed or upgraded Cisco ACI Virtual Edge.

3.2(9f) and later

CSCuu17314

CDP is not enabled on the management interfaces for the leaf switches and spine switches.

3.2(9b) and later

CSCvd43548

The stats for a given leaf switch rule cannot be viewed if a rule is double-clicked.

3.2(9b) and later

CSCvd66359

The Port ID LLDP Neighbors panel displays the port ID when the interface does not have a description. Example:  Ethernet 1/5, but if the interface has description, the Port ID property shows the Interface description instead of the port ID.

3.2(9b) and later

CSCve84297

A service cannot be reached by using the APIC out-of-band management that exists within the 172.17.0.0/16 subnet.

3.2(9b) and later

CSCvf70362

This enhancement is to change the name of "Limit IP Learning To Subnet" under the bridge domains to be more self-explanatory.

Original :

    Limit IP Learning To Subnet: [check box]

Suggestion :

    Limit Local IP Learning To BD/EPG Subnet(s): [check box]

3.2(9b) and later

CSCvg00627

A tenant's flows/packets information cannot be exported.

3.2(9b) and later

CSCvg35344

Requesting an enhancement to allow exporting a contract by right clicking the contract itself and choosing "Export Contract" from the right click context menu. The current implementation of needing to right click the Contract folder hierarchy to export a contract is not intuitive.

3.2(9b) and later

CSCvg70246

When configuring an L3Out under a user tenant that is associated with a VRF instance that is under the common tenant, a customized BGP timer policy that is attached to the VRF instance is not applied to the L3Out (BGP peer)  in the user tenant.

3.2(9b) and later

CSCvg81020

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

3.2(9b) and later

CSCvh52046

This is an enhancement to allow for text-based banners for the Cisco APIC GUI login screen.

3.2(9b) and later

CSCvh54578

For a client (browser or ssh client) that is using IPv6, the Cisco APIC aaaSessionLR audit log shows "0.0.0.0" or some bogus value.

3.2(9b) and later

CSCvi20535

When a VRF table is configured to receive leaked external routes from multiple VRF tables, the Shared Route Control scope to specify the external routes to leak will be applied to all VRF tables. This results in an unintended external route leaking. This is an enhancement to ensure the Shared Route Control scope in each VRF table should be used to leak external routes only from the given VRF table.

3.2(9b) and later

CSCvi82903

When authenticating with the Cisco APIC using ISE (TACACS), all logins over 31 characters fail.

3.2(9b) and later

CSCvi95657

On modifying a service parameter, the Cisco APIC sends 2 posts to the backend. The first post deletes all of the folders and parameters. The second post adds all of the remaining modified folders and parameters to the backend. These 2 posts will disrupt the running traffic.

3.2(9b) and later

CSCvj09453

The actrlRule is has the wrong destination.

3.2(9b) and later

CSCvj56726

The connectivity filter configuration of an access policy group is deprecated and should be removed from GUI.

3.2(9b) and later

CSCvk04072

There is no record of who acknowledged a fault in the Cisco APIC, nor when the acknowledgement occurred.

3.2(9b) and later

CSCvk18014

The action named 'Launch SSH' is disabled when a user with read-only access logs into the Cisco APIC.

3.2(9b) and later

CSCvm56946

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

3.2(9b) and later

CSCvm83669

There is a VLAN overlapping scenario. After configuring new static ports and a physical domain under an existing EPG, there is a Layer 2 loop. This issue is due to an FD VLAN encapsulation mismatch on two leaf switches.

3.2(9b) and later

CSCvn07827

Permament License Reservation (PLR) fails after upgrading to a Cisco APIC 4.0 release.

3.2(9b) and later

CSCvo24284

Fault delegates are raised on the Cisco APIC, but the original fault instance is already gone because the affected node has been removed from the fabric.

3.2(9b) and later

CSCvp01778

Access policy resolutions reveal unexpected results due to the existence of connectivity filters that are hidden from the UI. Depending on the VLANs tied to the AEPs/domains, this can result in unexpected outages as VLANs are pulled and 'invalid path' faults are flagged.

3.2(9b) and later

CSCvp24142

The Nginx process generates cores on the switches and the process will restart automatically. The core file from the switches gets collected and moved to the APIC, which drains the memory. You might need to remove the collected core files manually from the APIC to free up space.

3.2(9b) and later

CSCvp26694

A leaf switch gets upgraded when a previously-configured maintenance policy is triggered.

3.2(9b) and later

CSCvp62048

New port groups in VMware vCenter may be delayed when pushed from the Cisco APIC.

3.2(9b) and later

CSCvq39922

Specific operating system and browser version combinations cannot be used to log in to the APIC GUI.

Some browsers that are known to have this issue include (but might not be limited to) Google Chrome version 75.0.3770.90 and Apple Safari version 12.0.3 (13606.4.5.3.1).

3.2(9b) and later

CSCvq57942

In a RedHat OpenStack platform deployment running the Cisco ACI Unified Neutron ML2 Plugin and with the CompHosts running OVS in VLAN mode, when toggling the resolution immediacy on the EPG<->VMM domain association (fvRsDomAtt.resImedcy) from Pre-Provision to On-Demand, the encap VLANs (vlanCktEp mo's) are NOT programmed on the leaf switches.

This problem surfaces sporadically, meaning that it might take several resImedcy toggles between PreProv and OnDemand to reproduce the issue.

3.2(9b) and later

CSCvq63415

Disabling dataplane learning is only required to support a policy-based redirect (PBR) use case on pre-"EX" leaf switches.  There are few other reasons otherwise this feature should be disabled.  There currently is no confirmation/warning of the potential impact that can be caused by disabling dataplane learning.

3.2(9b) and later

CSCvq74727

When making a configuration change to an L3Out (such as contract removal or addition), the BGP peer flaps or the bgpPeerP object is deleted from the leaf switch.  In the leaf switch policy-element traces, 'isClassic = 0, wasClassic =1' is set post-update from the Cisco APIC.

3.2(9b) and later

CSCvq80820

A previously-working traffic is policy dropped after the subject is modified to have the "no stats" directive.

3.2(9b) and later

CSCvq88632

This is an enhancement request for allowing DVS MTU to be configured from a VMM domain policy and be independent of fabricMTU.

3.2(9b) and later

CSCvr19693

When configuring local SPAN in access mode using the GUI or CLI and then running the "show running-config monitor access session<session>" command, the output does not include all source span interfaces.

3.2(9b) and later

CSCvr30815

vmmPLInf objects are created with epgKey's and DN's that have truncated EPG names ( truncated at ".").

3.2(9b) and later

CSCvr36851

Descending option will not work for the Static Ports table. Even when the user clicks descending, the sort defaults to ascending.

3.2(9b) and later

CSCvr38278

When using AVE with Cisco APIC, fault F0214 gets raised, but there is no noticeable impact on AVE operation:

descr: Fault delegate: Operational issues detected for OpFlex device: ..., error: [Inventory not available on the node at this time]

3.2(9b) and later

CSCvr85515

When trying to track an AVE endpoint IP address, running the "show endpoint ip x.x.x.x" command in the Cisco APIC CLI to see the IP address and checking the IP address on the EP endpoint in the GUI shows incorrect or multiple VPC names.

3.2(9b) and later

CSCvr94614

There is a minor memory leak in svc_ifc_policydist when performing various tenant configuration removals and additions.

3.2(9b) and later

CSCvr96785

Configuring a static endpoint through the Cisco APIC CLI fails with the following error:

Error: Unable to process the query, result dataset is too big

Command execution failed.

3.2(9b) and later

CSCvr98638

When migrating an AVS VMM domain to Cisco ACI Virtual Edge, the Cisco ACI Virtual Edge that gets deployed is configured in VLAN mode rather than VXLAN Mode.  Because of this, you will see faults for the EPGs with the following error message:

"No valid encapsulation identifier allocated for the epg"

3.2(9b) and later

CSCvs03055

While configuring a logical node profile in any L3Out, the static routes do not have a description.

3.2(9b) and later

CSCvs10076

An error is raised while building an ACI container image because of a conflict with the /opt/ciscoaci-tripleo-heat-templates/tools/build_openstack_aci_containers.py package.

3.2(9b) and later

CSCvs16565

An endpoint is unreachable from the leaf node because the static pervasive route (toward the remote bridge domain subnet) is missing.

3.2(9b) and later

CSCvs21834

Randomly, the Cisco APIC GUI alert list shows an incorrect license expiry time.Sometimes it is correct, while at others times it is incorrect.

3.2(9b) and later

CSCvs29366

For a DVS with a controller, if another controller is created in that DVS using the same host name, the following fault gets generated: "hostname or IP address conflicts same controller creating controller with same name DVS".

3.2(9b) and later

CSCvs29556

When logging into the Cisco APIC using "apic#fallback\\user", the "Error: list index out of range" log message displays and the lastlogin command fails. There is no operational impact.

3.2(9b) and later

CSCvs32589

In Cisco ACI Virtual Edge, there are faults related to VMNICs. On the Cisco ACI Virtual Edge domain, there are faults related to the HpNic, such as "Fault F2843 reported for AVE | Uplink portgroup marked as invalid".

3.2(9b) and later

CSCvs47757

The plgnhandler process crashes on the Cisco APIC, which causes the cluster to enter a data layer partially diverged state.

3.2(9b) and later

CSCvs48552

When physical domains and external routed domains are attached to a security domain, these domains are mapped as associated tenants instead of associated objects under Admin > AAA > security management > Security domains.

3.2(9b) and later

CSCvs55753

A Cisco ACI leaf switch does not have MP-BGP route reflector peers in the output of "show bgp session vrf overlay-1". As a result, the switch is not able to install dynamic routes that are normally advertised by MP-BGP route reflectors. However, the spine switch route reflectors are configured in the affected leaf switch's pod, and pod policies have been correctly defined to deploy the route reflectors to the leaf switch. Additionally, the bgpPeer managed objects are missing from the leaf switch's local MIT.

3.2(9b) and later

CSCvs57061

In a GOLF configuration, when an L3Out is deleted, the bridge domains stop getting advertised to the GOLF router even though another L3Out is still active.

3.2(9b) and later

CSCvs66244

The CLI command "show interface x/x switchport" shows VLANs configured and allowed through a port. However, when going to the GUI under Fabric > Inventory > node_name > Interfaces > Physical Interfaces > Interface x/x > VLANs, the VLANs do not show.

3.2(9b) and later

CSCvs76244

The tmpfs file system that is mounted on /data/log becomes 100% utilized.

3.2(9b) and later

CSCvs78996

The policy manager (PM) may crash when use testapi to delete MO from policymgr db.

3.2(9b) and later

CSCvs81907

SNMP does not respond to GETs or sending traps on one or more Cisco APICs despite previously working properly.

3.2(9b) and later

CSCvt00796

The policymgr DME process can crash because of an OOM issue, and there are many pcons.DelRef managed objects in the DB.

3.2(9b) and later

CSCvt07565

The eventmgr database size may grow to be very large (up to 7GB). With that size, the Cisco APIC upgrade will take 1 hour for the Cisco APIC node that contains the eventmgr database.

In rare cases, this could lead to a failed upgrade process, as it times out while working on the large database file of the specified controller.

3.2(9b) and later

CSCvt13978

VPC protection created in prior to the 2.2(2e) release may not to recover the original virtual IP address after fabric ID recovery. Instead, some of vPC groups get a new vIP allocated, which does not get pushed to the leaf switch. The impact to the dataplane does not come until the leaf switch had a clean reboot/upgrade, because the rebooted leaf switch gets a new virtual IP that is not matched with a vPC peer. As a result, both sides bring down the virtual port channels, then the hosts  behind the vPC become unreachable.

3.2(9b) and later

CSCvt19061

Updating the interface policy group breaks LACP if eLACP is enabled on a VMM domain. If eLACP was enabled on the domain,  Creating, updating, or removing an interface policy group with the VMM AEP deletes the basic LACP that is used by the domain.

3.2(9b) and later

CSCvt37066

When migrating an EPG from one VRF table to a new VRF table, and the EPG keeps the contract relation with other EPGs in the original VRF table. Some bridge domain subnets in the original VRF table get leaked to the new VRF table due to the contract relation, even though the contract does not have the global scope and the bridge domain subnet is not configured as shared between VRF tables. The leaked static route is not deleted even if the contract relation is removed.

3.2(9b) and later

CSCvt40736

The login history of local users is not updated in Admin > AAA > Users > (double click on local user) Operational > Session.

3.2(9b) and later

CSCvt55566

In the Cisco APIC GUI, after removing the Fabric Policy Group from "System > Controllers > Controller Policies > show usage", the option to select the policy disappears, and there is no way in the GUI to re-add the policy.

3.2(9b) and later

CSCvu01452

The MD5 checksum for the downloaded Cisco APIC images is not verified before adding it to the image repository.

3.2(9b) and later

CSCvu21530

Protocol information is not shown in the GUI when a VRF table from the common tenant is being used in any user tenant.

3.2(9b) and later

CSCvu39569

The following error is encountered when accessing the Infrastructure page in the ACI vCenter plugin after inputting vCenter credentials.

"The Automation SDK is not authenticated"

VMware vCenter plug-in is installed using powerCLI. The following log entry is also seen in vsphere_client_virgo.log on the VMware vCenter:

/var/log/vmware/vsphere-client/log/vsphere_client_virgo.log

 [ERROR] http-bio-9090-exec-3314       com.cisco.aciPluginServices.core.Operation                       

sun.security.validator.ValidatorException: PKIX path validation failed:

java.security.cert.CertPathValidatorException: signature check failed

3.2(9b) and later

CSCvu50088

When trying to assign a description to a FEX downlink/host port using the Config tab in the Cisco APIC GUI, the description will get applied to the GUI, but it will not propagate to the actual interface when queried using the CLI or GUI.

3.2(9b) and later

CSCvu62465

For an EPG containing a static leaf node configuration, the Cisco APIC GUI returns the following error when clicking the health of Fabric Location:

Invalid DN topology/pod-X/node-Y/local/svc-policyelem-id-0/ObservedEthIf, wrong rn prefix ObservedEthIf at position 63

3.2(9b) and later

CSCvu74566

There is a BootMgr memory leak on a standby Cisco APIC. If the BootMgr process crashes due to being out of memory, it continues to crash, but system will not be rebooted. After the standby Cisco APIC is rebooted by hand, such as by power cycling the host using CIMC, the login prompt of the Cisco APIC will be changed to localhost and you will not be able to log into the standby Cisco APIC.

3.2(9b) and later

CSCvv25475

After a delete/add of a Cisco ACI-managed DVS, dynamic paths are not programmed on the leaf switch and the compRsDlPol managed object has a missing target. The tDn property references the old DVS OID instead of the latest value.# moquery -c compRsDlPol

3.2(9b) and later

CSCvv62861

A leaf switch reloads due to an out-of-memory condition after changing the contract scope to global.

3.2(9b) and later

CSCvw33061

Traffic loss is observed from multiple endpoints deployed on two different vPC leaf switches.

3.2(9b) and later

CSCvs10395

Leaf switch downlinks all go down at one time due to FabricTrack.

3.2(9b)

CSCvs31125

When using QSFP-100G-PSM4-S transceivers in an N9K-X9736C-FX linecard that is running ACI code, link flaps may be seen intermittently.

3.2(9b)

CSCvt13077

A downgrade fails for a standby APIC when downgraded from release 3.2(9b).

3.2(9b)

CSCvs10395

Leaf switch downlinks all go down at one time due to FabricTrack.

3.2(9f)

CSCvs31125

When using QSFP-100G-PSM4-S transceivers in an N9K-X9736C-FX linecard that is running ACI code, link flaps may be seen intermittently.

3.2(9f)

CSCvs47906

The following fault is raised on the switch: "F3525: High SSD usage observed. Please check switch activity and contact Cisco Technical Support about high SSD usage."

3.2(9f)

CSCvt10029

This is an enhancement to include the managed object class name and isPersisted attribute in DME log line.

3.2(9f)

CSCvt13077

A downgrade fails for a standby APIC when downgraded from release 3.2(9b).

3.2(9f)

CSCvj75392

Cisco APIC can be seen repeatedly logging into the RHV controller at a rapid rate in the RHV Event tab. This can also lead to a memory usage increase on the controller, as each login is a new session. Specifically, the Postgres process on the RHV controller increases.

3.2(9b)

CSCvn64048

The policymgr process in the APIC resets and results in a core file. Configurations can be missed if the core file is generated during a configuration import or during configuration steps.

3.2(9b)

CSCvp56973

The endpoints of the VMs behind an AVS tunnel are not learned in EPM on the leaf switch.

3.2(9b)

CSCvp64280

A vulnerability in the fabric infrastructure VLAN connection establishment of the Cisco Nexus 9000 Series Application Centric Infrastructure (ACI) Mode Switch Software could allow an unauthenticated, adjacent attacker to bypass security validations and connect an unauthorized server to the infrastructure VLAN.

The vulnerability is due to insufficient security requirements during the Link Layer Discovery Protocol (LLDP) setup phase of the infrastructure VLAN. An attacker could exploit this vulnerability by sending a malicious LLDP packet on the adjacent subnet to the Cisco Nexus 9000 Series Switch in ACI mode. A successful exploit could allow the attacker to connect an unauthorized server to the infrastructure VLAN, which is highly privileged. With a connection to the infrastructure VLAN, the attacker can make unauthorized connections to Cisco Application Policy Infrastructure Controller (APIC) services or join other host endpoints.

Cisco has released software updates that address this vulnerability. There are workarounds that address this vulnerability.

This advisory is available at the following link:

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190703-n9kaci-bypass

3.2(9b)

CSCvp64857

A vulnerability in the REST API for software device management in Cisco Application Policy Infrastructure Controller (APIC) Software could allow an authenticated, remote attacker to escalate privileges to root on an affected device.

The vulnerability is due to incomplete validation and error checking for the file path when specific software is uploaded. An attacker could exploit this vulnerability by uploading malicious software using the REST API. A successful exploit could allow an attacker to escalate their privilege level to root. The attacker would need to have the administrator role on the device.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. This advisory is available at the following link:

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190703-ccapic-restapi

3.2(9b)

CSCvp71531

Fault F0467 is raised with the following description:

Configuration failed for ... due to Encap Already Used in Another EPG

3.2(9b)

CSCvp88848

During an SSH connection to the Cisco APIC, the following message appears in CLI:

<html><head><title>502 Bad Gateway</title></head><body bgcolor="white"><center><h1>502 Bad Gateway</h1></center><hr><center>nginx/1.10.3</center></body></html>

3.2(9b)

CSCvq04903

Traffic to newly provisioned floating IP addresses is dropped for up to an hour.

3.2(9b)

CSCvq05143

Using a PBR service graph with ASA in two-arm mode. After upgrading from release 12.3(1) to 13.1 to 13.2(6i), the service graph (in the common tenant) has some faults. The service graph is working for previously-configured EPGs (verified by checking traffic that is redirected to the firewall), but new EPGs cannot be applied to the service graph. The service graph state is also "not applied".

One of the faults mentions that the service graph contract cannot be used as provider and consumer and that the contract is only supported in single-node PBR with one arm. The contract is not being applied in any vzAny consumer/provider. The "Epp not found. Retry or abort task" error appears in the policymanager. Adding an ARP filter on the contract does not trigger anything, although the modification is seen in the policy distributor.

3.2(9b)

CSCvq14177

The Hyper-V agent is in the STOPPED state. Hyper-V agent logs indicate that process is stopping at the "Set-ExecutionPolicy Unrestricted" command.

3.2(9b)

CSCvq23610

In addition to the "Enforce Password Change interval" setting, APIC has another setting, "Minimum period between password changes," which is by default set to 24 hours. When "Enforce Password Change interval" is disabled, the backend enforces the "Minimum period between password changes" setting.

3.2(9b)

CSCvq36114

Changing the user credentials for a Red Hat VMM domain may result in a previous username still being used to authenticate with the Red Hat controller.

3.2(9b)

CSCvq41830

NGINX spikes to 100% CPU usage.

3.2(9b)

CSCvq53010

The vmmmgr process on the APICs crash due to an unhandled HTML tag "hr" response from a Red Hat Controller that is tied to a Red Hat VMM domain.

3.2(9b)

CSCvq94187

If a switch upgrade is triggered after the series of steps outlined in this bug's conditions, the switch nodes may get stuck in a reboot loop where the bootscript process pushes the bootscript file (using DCHP), which tells the switch to boot into the default version. However, the APIC policy discovers the switch and finds that it has not yet been upgraded to the upgrade target version.

3.2(9b)

CSCvq99246

On Cisco APIC release 4.1(2m) and VMware release 6.7.0.3, the VMM process generates a core while attempting to perform VMM integration.

3.2(9b)

CSCvr01886

The VMMMGR process continuously crashes and causes the cluster health to become partially diverged.

3.2(9b)

CSCvr05720

With Cisco ACI Virtual Edge (when not part of a Cisco ACI vPod), after using vMotion to migrate virtual machines, there is traffic loss and a live core gets generated on opflexelem on the TOR switch.

3.2(9b)

CSCvr41750

Policies may take a long time (over 10 minutes) to get programmed on the leaf switches. In addition, the APIC pulls inventory from the VMware vCenter repeatedly, instead of following the usual 24 hour interval.

3.2(9b)

CSCvr51121

If the current VMware vCenter crashes and is not recoverable, then a new VMware vCenter with an identical configuration is built, the Cisco APIC pushes  the DVS and Quarantine port-groups. However, the APIC does not push the EPG port group.

3.2(9b)

CSCvr65035

The last APIC in the cluster gets rebooted when APIC-1 is decommissioned due to some issue seen on APIC-1 while upgrading. In addition, after decommissioning APIC-1, the other APICs still wait for APIC-1 to get upgraded.

3.2(9b)

CSCuo52668

The Cisco APIC does not validate duplicate IP addresses that are assigned to two device clusters. The communication to devices or the configuration of service devices might be affected.

3.2(9b) and later

CSCuo79243

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

3.2(9b) and later

CSCuo79250

The node ID policy can be replicated from an old appliance that is decommissioned when it joins a cluster.

3.2(9b) and later

CSCup47703

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

3.2(9b) and later

CSCup79002

The hostname resolution of the syslog server fails on leaf and spine switches over in-band connectivity.

3.2(9b) and later

CSCuq21360

Following a FEX or switch reload, configured interface tags are no longer configured correctly.

3.2(9b) and later

CSCur39124

Switches can be downgraded to a 1.0(1) version if the imported configuration consists of a firmware policy with a desired version set to 1.0(1).

3.2(9b) and later

CSCur71082

If the Cisco APIC is rebooted using the CIMC power reboot, the system enters into fsck due to a corrupted disk.

3.2(9b) and later

CSCus15627

The Cisco APIC Service (ApicVMMService) shows as stopped in the Microsoft Service Manager (services.msc in control panel > admin tools > services). This happens when a domain account does not have the correct privilege in the domain to restart the service automatically.

3.2(9b) and later

CSCut51929

The traffic destined to a shared service provider endpoint group picks an incorrect class ID (PcTag) and gets dropped.

3.2(9b) and later

CSCuu09236

Traffic from an external Layer 3 network is allowed when configured as part of a vzAny (a collection of endpoint groups within a context) consumer.

3.2(9b) and later

CSCuu61998

Newly added microsegment EPG configurations must be removed before downgrading to a software release that does not support it.

3.2(9b) and later

CSCuu64219

Downgrading the fabric starting with the leaf switch will cause faults such as policy-deployment-failed with fault code F1371.

3.2(9b) and later

CSCva32534

Creating or deleting a fabricSetupP policy results in an inconsistent state.

3.2(9b) and later

CSCva60439

After a pod is created and nodes are added in the pod, deleting the pod results in stale entries from the pod that are active in the fabric. This occurs because the Cisco APIC uses open source DHCP, which creates some resources that the Cisco APIC cannot delete when a pod is deleted.

3.2(9b) and later

CSCva86794

When a Cisco APIC cluster is upgrading, the Cisco APIC cluster might enter the minority status if there are any connectivity issues. In this case, user logins can fail until the majority of the Cisco APICs finish the upgrade and the cluster comes out of minority.

3.2(9b) and later

CSCva97082

When downgrading to a 2.0(1) release, the spines and its interfaces must be moved from infra L3out2 to infra L3out1. After infra L3out1 comes up, delete L3out2 and its related configuration, and then downgrade to a 2.0(1) release.

3.2(9b) and later

CSCvb39702

No fault gets raised upon using the same encapsulation VLAN in a copy device in tenant common, even though a fault should get raised.

3.2(9b) and later

CSCvg41711

In the leaf mode, the command "template route group <group-name> tenant <tenant-name>" fails, declaring that the tenant passed is invalid.

3.2(9b) and later

CSCvg79127

When First hop security is enabled on a bridge domain, traffic is disrupted.

3.2(9b) and later

CSCvg81856

Cisco ACI Multi-Site Orchestrator BGP peers are down and a fault is raised for a conflicting rtrId on the fvRtdEpP managed object during L3extOut configuration.

3.2(9b) and later

CSCvh76076

The PSU SPROM details might not be shown in the CLI upon removal and insertion from the switch.

3.2(9b) and later

CSCvh93612

If two intra-EPG deny rules are programmed—one with the class-eq-deny priority and one with the class-eq-filter priority—changing the action of the second rule to "deny" causes the second rule to be redundant and have no effect. The traffic still gets denied, as expected.

3.2(9b) 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.

3.2(9b) 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.

3.2(9b) and later

CSCvr57103

The CiscoAVS_4.10-5.2.1.SV3.4.10-pkg  package has signature issues during installation.

3.2(9b) and later

Product ID

Description

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)