Cisco Application Policy Infrastructure Controller, Release 3.1(1), Release Notes

December 9, 2022

In the Open Bugs section, added bug CSCvw33061.

August 29, 2022

In the Miscellaneous Compatibility Information section, for CIMC HUU ISO, added 3.0(3f).

February 3, 2021

In the Miscellaneous Compatibility Information section, for CIMC HUU ISO, deleted the bullets that mentioned APIC-M3 and APIC-M4. These servers are not supported in this release.

October 4, 2019

In the Miscellaneous Guidelines section, added the following bullet:

■      When you create an access port selector in a leaf interface rofile, the fexId property is configured with a default value of 101 even though a FEX is not connected and the interface is not a FEX interface. The fexId property is only used when the port selector is associated with an infraFexBndlGrp managed object.

October 3, 2019

In the Miscellaneous Guidelines section, added the bullet that begins as follows:

■      Fabric connectivity ports can operate at 10G or 25G speeds (depending on the model of the APIC server) when connected to leaf switch host interfaces.

September 17, 2019

3.1(1i): In the Open Bugs section, added bug CSCuu17314, CSCve84297, and CSCvg70246.

August 5, 2019

3.1(1i): In the Open Bugs section, added bug CSCvj76503.

November 21, 2018

3.1(1i): In the Open Bugs section, added bug CSCvn15374.

September 21, 2018

In the New Software Features section, for the tracking service nodes with policy-based redirect and support for hashing algorithms feature, specified that the feature is supported only on EX and FX switches.

September 18, 2018

In the Changes in Behavior section, added the following bullet:

■      The ACI Optimizer feature is deprecated.

June 7, 2018

3.1(1i): In the Open Bugs section, added bug CSCvj75897.

March 30, 2018

In the New Software Features section, for the " Configuring flood in encapsulation for all protocols and proxy ARP across encapsulations" feature, changed " Application Spine Engine (ASE)" to "Application Leaf Engine (ALE)."

In the Miscellaneous Compatibility Information section, changed the Cisco AVS release to 5.2(1)SV3(3.20) and added Cisco ACI Virtual Edge 1.1(1a).

March 12, 2018

In the New Software Features section, removed the following item:

Cisco ACI Multi-Site support on the Cisco N9K-C9364C switch and N9K-C9508-FM-E2  and N9K-C9516-FM-E2 fabric modules

This text was erroneously included.

February 16, 2018

In the New Software Features section, for the fast link failover policy feature, added the following limitation:

This feature is not support with port profiles nor remote leaf switches. When the Fast Link Failover policy is enabled, configuring SPAN on individual uplinks does not work.

February 15, 2018

In the New Software Features section, added Read-Only Mode VMM Domain for VMware VDS.

February 9, 2018

In the New Software Features section, added the following items:

Cisco Tetration Analytics support for network performance, monitoring, and diagnostic

Cisco Tetration Analytics support on the Cisco Nexus 9500-series switches with the N9K-X9736C-FX linecard

Removed the following item because the feature was added in the 3.0(1) release:

Cisco Tetration Analytics support on the Cisco N9K-C9348GC-FXP switch

February 7, 2018

In the Changes in Behavior section, added the following bullet:

■      The following global policies were moved from the Fabric tab > Access Policies subtab > Global Policies folder to the System tab > System Settings subtab: …

January 3, 2018

Modification in New Software Features: Added note. Multipod and Cisco ACI Multi-Site together are not yet supported on Cisco N9K-C9364C switch.

December 22, 2017

3.1(1i): Release 3.1(1i) became available.

Active sessions

This release adds support for monitoring GUI user active sessions. This feature is located under the System > Active Sessions tab.

See the Cisco APIC online help for more information.

None.

Additional NAT firewall public IP addresses for a VRF instance

You can allocate additional public IP addresses for use with NAT rules. You can request this public IP address from any EPG where NAT is enabled, so it is available for all EPGs in the VRF instance.

We recommend that the destination IP address of the NAT rule points only to an endpoint within the EPG and not somewhere else in the VRF instance.

BFD support on spine switches

This release adds support for Bidirectional Forwarding Detection (BFD) on spine switch.

For more information, see the Cisco APIC Layer 3 Networking Configuration Guide.

None.

Cisco Application Centric Infrastructure Virtual Edge

This release supports Cisco ACI Virtual Edge, the next generation of the Application Virtual Switch (AVS) for Cisco ACI environments. Cisco ACI Virtual Edge is a hypervisor-agnostic distributed virtual switch that runs in the user space as a service VM. It operates as a virtual leaf switch and is managed by the Cisco Application Policy Infrastructure Controller (APIC).

If you use VMware VDS or Cisco AVS, you can migrate to Cisco ACI Virtual Edge and can also run Cisco ACI Virtual Edge on top of the existing VMware VDS. Decoupling the Cisco ACI Virtual Edge from the kernel space makes Cisco ACI Virtual Edge adaptable to different hypervisors. It also facilitates upgrades because Cisco ACI Virtual Edge is no longer tied to hypervisor upgrades.

For more information, see the Cisco ACI Virtual Edge Release Notes.

■      Cisco ACI Virtual Edge is available only on the VMware hypervisor.

■      Cisco ACI Virtual Edge is supported with the latest VMware vSphere 6.0 build and later releases.

■      We you can install only one Cisco ACI Virtual Edge VM per host.

■      You should deploy Cisco ACI Virtual Edge on a local disk on the host.

■      VXLAN load-balancing will be supported after Cisco ACI Virtual Edge initial release.

■      The Cisco ACI Virtual Edge management interface must have an IPv4 address. It can optionally have an additional IPv6 address, but you cannot configure it only with an IPv6 address.

Cisco Tetration Analytics support for network performance, monitoring, and diagnostic

The Tetration platform uses rich dataplane telemetry from hardware sensors to provide network performance, monitoring, and diagnostics capability on a Cisco ACI fabric. The following features require Cisco Nexus 9300-FX switches and Cisco Nexus 9500 series switches with N9K-X9736C-FX linecards in the Cisco ACI mode:

■      Per queue and per link aggregate stats on: bandwidth, packet drop indicators, average and max latency

■      Maps flows to link topology and queue

■      Network topology visualization and drill down

■      End-to-end fabric view per flow

■      Per hop view of a flow

■      Time-series view for all the performance indicators including network topology

None.

Cisco Tetration Analytics support on the Cisco Nexus 9500-series switches with the N9K-X9736C-FX linecard

Cisco Tetration Analytics telemetry is now supported on the Cisco Nexus 9500-series switches with the N9K-X9736C-FX linecard.

None.

Cloud Foundry integration

Cloud Foundry integration with Cisco ACI is a beta feature that is visible in the Cisco APIC GUI.

This feature is not supported in this release. Contact Cisco for information about this feature.

Cloud Orchestrator Mode

This feature Provides a Loadbalancer-as-a-Service (LBaaS) and a Firewall-as-a-Service (FWaaS) interface to enable a standard set of parameters that creates a unified interface for configuring load balancers and firewalls in a service graph.

For more information, see the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide.

None.

Configuring flood in encapsulation for all protocols and proxy ARP across encapsulations

In this release, on the Cisco ACI switches with the Application Leaf Engine (ALE), all protocols are flooded in encapsulation. Multiple EPGs are now supported under one bridge domain with an external switch. When two EPGs share the same bridge domian and the Flood in Encapsulation option is turned on, the EPG flooding traffic does not reach the other EPG. It overcomes the challenges of using the Cisco ACI switches with the Virtual Connect (VC) tunnel network.

For more information, see the Cisco APIC Layer 2 Networking Configuration Guide.

None.

Control plane policing (CoPP) per interface per protocol

A CoPP configuration is now supported on a per interface and per protocol basis. The protocols supported are ARP, ICMP, CDP, LLDP, LACP, BGP, STP, BFD, and OSPF.

For more information, see the Cisco APIC Security Configuration Guide.

None.

Control plane policing (CoPP) prefilter

To protect against DDoS attacks, a CoPP prefilter profile is used on spine and leaf switches to filter access to authentication services based on specified sources and TCP ports. When the CoPP prefilter profile is deployed on a switch, the control plane traffic is denied by default. Only the traffic specified in the CoPP prefilter profile is permitted.

For more information, see the Cisco APIC Security Configuration Guide.

■      Only Ethernet type IPv4 or IPv6 packets can be matched in the egress TCAM. ARP and ND packets are not matched.

■      A total of 128 (wide key) entries can be included in the allowed list. However, some entries are reserved for internal use.

Converting uplink ports and downlink ports

Uplink and downlink conversion is supported on Cisco Nexus 9000-series switches with names that end in EX or FX, such as the N9K-C93180YC-EX switch. A FEX can be connected to a converted downlink ports.

For more information, see the Cisco Application Centric Infrastructure Fundamentals document.

None.

EthType IPv4 and IPv6 support

This release adds support for the IPv4 and IPv6 ARP security filter type.

None.

Fast link failover policy

A fast link failover policy is applicable to uplinks on Cisco N9K-C93180YC-EX and N9K-C93180YC-FX platforms only. The policy efficiently load balances the traffic based on the uplink MAC status. With this functionality, the switch performs Layer 2 or Layer 3 lookup and it provides an output Layer 2 interface (uplinks) based on the packet hash algorithm by considering the uplink status. This functionality reduces the data traffic convergence to less than 10 milliseconds.

This feature is not support with port profiles nor remote leaf switches. When the Fast Link Failover policy is enabled, configuring SPAN on individual uplinks does not work.

Favorites

You can now bookmark commonly-used GUI pages, which you can then access quickly from the Manage my profile > Favorites menu. You bookmark a page by clicking the star icon in the upper right of the page.

Not all pages can be bookmarked.

FIPS SHA1 key support

When Federal Information Processing Standards (FIPS) is enabled, SHA1 key is supported for NTP authentication.

None.

First-hop security

Starting with Cisco AVS release 5.2(1)SV3(3.20), the first-hop security (FHS) feature is supported. The FHS feature set provides improved management and IPv4 link security over the Layer 2 links. In a service provider environment, FHS controls address assignment and derived operations, such as duplicate address detection (DAD) and address resolution (AR). Cisco AVS is an FHS policy enforcer for virtual endpoints. FHS includes the following security features: IP address inspection, source guard, and ARP learning.

■      FHS enforcement is not supported for IPv6 address family on AVS.

■      FHS is not supported with micro-segmentation.

■      FHS endpoint entry is not retained when a port is detached and attached to VMware vCenter.

■      Cisco AVS does not detect duplicate addresses across ESX hosts.

■      A static virtual endpoint (vep) configuration is required when VMware fault tolerance is enabled for virtual machines with trust ports.

High dual stack

The high dual stack option was added to the forwarding scale profile policy to provide scalability of up to 24k endpoints for IPv6 configurations and up to 64k endpoints for IPv4 configurations. This option also increases the LPM scale to 38K for both IPv4 and IPv6.

For more information, see the Cisco APIC Forwarding Scale Profile Policy document.

■      The high dual stack profile reduces the policy scale to 8k.

■      High dual stack does not support multicast.

■      Switches configured with high dual stack must be manually reloaded to enable the profile.

ICMP tracking support

TCP and ICMP protocol types are now used to track the Redirect Destination node.

For more information, see the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide.

None.

IP SLA monitoring support

Switches internally use the Cisco IP SLA monitoring feature to support policy-based redirect (PBR) tracking.

For more information, see the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide.

None.

Launch Stats

You can view the stats of a specific physical interface by going to the Fabric > Inventory tab, then navigating to pod_name > leaf_name > Interfaces. Click the button in the Stats column that corresponds to the desired interface.

None.

Layer 3 multicast support for Fabric Extenders

Multicast sources or receivers connected to Fabric Extender (FEX) ports are supported.

For more information, see the Cisco APIC Layer 3 Networking Configuration Guide.

None.

LDAP group map

The LDAP group map feature enables you to add LDAP configurations using active directory (AD) groups in place of Cisco attribute-value (AV) pairs.

For more information, see the Cisco APIC Security Configuration Guide.

This feature does not require making changes to the LDAP server for use with the Cisco APIC.

Location-aware policy-based redirect

When you enable location-aware redirection and you specify Pod IDs, all of the redirect destinations in the Layer 4 to Layer 7 policy-based redirect policy will have pod awareness.

For more information, see the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide.

None.

MACsec support

MACsec provides MAC-layer encryption over wired networks by using out-of-band methods for encryption keying. The MACsec Key Agreement (MKA) Protocol provides the required session keys and manages the required encryption keys.

For more information, see the Cisco APIC Layer 2 Networking Configuration Guide.

None.

Multipod support on the Cisco N9K-C9364C switch and N9K-C9508-FM-E2  and N9K-C9516-FM-E2 fabric modules

This release adds support for multipod on the Cisco N9K-C9364C switch and N9K-C9508-FM-E2 and N9K-C9516-FM-E2 fabric modules.

Note: Multipod and Cisco ACI Multi-Site together are currently not supported on the Cisco N9K-C9364C switch.

None.

Nesting in VMware for OpenShift and Kubernetes

This release adds support for nesting in VMware for OpenShift and Kubernetes.

None.

NTP Authentication support

This release adds support for HMAC-NTP authentication.

For more information, see the Cisco APIC Basic Configuration Guide.

None.

NTP server

This feature enables client switches to act as NTP servers to provide NTP time information to downstream clients.

For more information, see the Cisco APIC Basic Configuration Guide.

None.

OpenShift support for containers on Cisco ACI

This release introduces native Cisco ACI support for container orchestration systems. This support includes the following features:

■      Containers have direct access to the ACI policy model.

■      Containers, VMs, and physical devices have seamless integration on a Cisco ACI fabric.

■      Cisco APIC supports native policy semantics.

■      Key network capabilities are provided to operate in this ecosystem. In particular, there is load balancing for both internal and external services.

None.

Policy-based redirect support for service nodes in consumer and provider bridge domains

Bridge domains that contain a consumer or provider also support service nodes. Therefore, you are not required to provision separate service node bridge domains any longer.

For more information, see the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide.

None.

Port configuration improvements

In the GUI, port configuration is improved to show operation and configuration. When you view a leaf switch within a pod under Fabric > Inventory, you can now click on a port to see information about that port.

See the Cisco APIC online help for more information.

None.

Quick Start workflows for setting up node, remote leaf switch, and multipod

This release includes Quick Start workflows for setting up node, remote leaf switch, and multipod. You can now access the workflows by navigating to Fabric > Inventory, then expanding Quick Start.

For more information, see the Cisco APIC Layer 3 Networking Configuration Guide.

None.

Read-Only Mode VMM Domain for VMware VDS

This release adds support for creating a read-only mode VMM domain for VMware VDS. This enables you to view information about a DVS in VMware vCenter that is not managed by the Cisco APIC. You create a read-only VMM domain by setting the access mode when you create the domain.

■      If you want to create a read-only VMM domain, the domain must have the same name as the DVS in VMware vCenter, and the DVS must be inside a network folder with the same name.

■      You can associate EPGs to a read-only VMM domain and apply policies to it. However, the policies are not pushed to the DVS in VMware vCenter.

■      Faults are not raised for a read-only VMM domain.

Red Hat virtualization support

This release supports Red Hat Virtualization (RHV) integration. RHV--formerly Red Hat Enterprise Virtualization--is an open-source virtualization solution. It is based on the Kernel-based Virtual Machine (KVM) hypervisor and the oVirt management platform. It includes the RHV host and the RHV manager (RHVM).

The concept of endpoint groups in Cisco ACI is equivalent to a network in RHV.

We recommend that you use RHV release 4.1.6 or later.

Remote leaf switches

With a Cisco ACI fabric deployed, you can extend Cisco ACI services and Cisco APIC management to remote data centers with Cisco ACI leaf switches that have no local spine switch or Cisco APIC attached. All policies deployed in the main data center are deployed on the remote switches, which behave like local leaf switches belonging to a pod.

For more information, see the Cisco APIC Layer 3 Networking Configuration Guide.

If you have remote leaf switches deployed, if you downgrade the Cisco APIC software from release 3.1(1) or later to an earlier release that does not support the remote leaf feature, you must decommission the nodes before downgrading.

For more information on decommissioning switches, see “Decommissioning and Recommissioning Switches” in the Cisco APIC Troubleshooting Guide.

Role-based access control integration for Cisco ACI VMware vCenter plug-in

Starting with this release, the Cisco ACI VMware vCenter plug-in supports enhanced role-based access control (RBAC) based on Cisco APIC user roles and security domains.

None.

RSA secure ID

This feature provides token-based password authentication.

For more information, see the Cisco APIC Security Configuration Guide.

None.

Shared GOLF

For Cisco APIC sites in a Cisco ACI Multi-Site topology, if stretched VRF instances share GOLF connections, guidelines are provided to avoid the risk of cross-VRF traffic issues.

For more information, see the “Cisco ACI GOLF” chapter in the Cisco APIC Layer 3 Networking Configuration Guide.

None.

SNMP Trap Aggregation

The SNMP trap aggregation feature allows SNMP traps from the fabric nodes to be delivered to one of the Cisco APICs in the cluster and allows the forwarding of SNMP traps received from the fabric nodes to the external destination.

For more information, see the Cisco APIC Basic Configuration Guide.

If you decommission Cisco APICs, the trap forward server will receive redundant traps.

Support for the deny action and the relative ordering of entries in the OSPF import route map

OSPF import route map has been enhanced to support the deny action in addition to the permit action. You can also create permit and deny entries in a specified order.

None.

Switch Virtual Interface (SVI) auto state

You can now enable the SVI auto state behavior. This allows the SVI state to be in the down state when all the ports in the VLAN go down.

None.

Tracking service nodes with policy-based redirect and support for hashing algorithms

The policy-based redirect feature (PBR) supports tracking service nodes and PBR also supports specific hashing algorithms.

For more information, see the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide.

This feature is supported only on EX and FX switches.

CSCuu17314

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

3.1(1i) and later

CSCvd43548

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

3.1(1i) 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.1(1i) 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.1(1i) and later

CSCvf32908

When using mongoDB for Cisco ACI apps, the app must be deleted before the upgrade and reinstalled after the upgrade to avoid corruption of application data.

3.1(1i) 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.1(1i) and later

CSCvf70411

A route will be advertised, but will not contain the tag value that is set from the VRF route tag policy.

3.1(1i) and later

CSCvf92483

This issue occurs while using the import-config file command on the CLI where the file is the output of export-config command. The file contains the output of show running-config of the scope where export-config was executed. The error occurs only when the file contains crypto commands, the Bash shell throws the error and hangs without returning the prompt.

3.1(1i) and later

CSCvg00627

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

3.1(1i) and later

CSCvg02551

When the IS-IS to OSPF Multi-Site CPTEP route leaking is not programmed, inter-site BGP session might go down on the spine switch. This behavior might cause traffic drop.

3.1(1i) 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.1(1i) and later

CSCvg37617

The zoning rule installation incorrectly permitted all of the traffic to and from the L3Out to EPG as the default permit without redirecting the traffic to the service node.

3.1(1i) 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.1(1i) and later

CSCvg53205

A fault for a 100% drop rate is observed for an endpoint-to-external IP address atomic counters policy after disabling/enabling a switch.

3.1(1i) and later

CSCvg56414

An external IP address-to-external IP address atomic counters policy does not give the results for the flow that matches the configured external IP addresses.

3.1(1i) and later

CSCvg60014

Clicking the Submit button in a wizard will fail if any of the entered values are invalid.

3.1(1i) and later

CSCvg60565

If a service graph is initially configured as uni-directional and later a filter is added and the service graph is made bi-direction, the service graph enters a faulty state.

3.1(1i) and later

CSCvg67522

When two different service chains (one for IPv4 traffic and the other for IPv6 traffic) are using the same exact forwarding path (the same bridge domain and VLAN on the service nodes), but different redirect policies (one for IPv4 and the other for IPv6), then the IP SLA objects might not be cleaned up when the contract is detached from the service graph.

3.1(1i) 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.1(1i) and later

CSCvg74082

A newly-created VFC shows the admin state as down.

3.1(1i) and later

CSCvg75150

A service graph is in the applied state even if the VRF instance associated with the consumer EGP or consumer-facing service node EPG gets deleted.

3.1(1i) and later

CSCvg79436

In Cloud Orchestrator Mode, dual stack (that is, IPv4 and IPv6) cannot be configured on the same interface.

3.1(1i) and later

CSCvg81020

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

3.1(1i) 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.1(1i) and later

CSCvg82738

Whenever a user expands a drop-down list that has many policies (>10K), the GUI tries to show all of them at once, which causes a timeout from the server, after which the server tries again. This process continues and the GUI becomes unresponsive.

3.1(1i) and later

CSCvg82990

The Cisco AVS DPA process might crash on AVS after upgrading to a 3.1.x release. This does not always occur. When it does occur, the DPA process restarts automatically.

3.1(1i) and later

CSCvg84464

There is an exhaustion of LPM entries due to the programming of an unnecessary EPG subnet gateway IP address.

3.1(1i) and later

CSCvg86073

With a 0.0.0.0/0 subnet and a specific subnet with an import route-map, the GUI shows only a 212.1.0.0/24 subnet.

3.1(1i) and later

CSCvg95080

A remote leaf switch TEP pool is not getting deleted if the remote leaf switches are decommissioned before deleting the vPC.

3.1(1i) and later

CSCvh00839

On importing an exported configuration, the import will succeed and might report a warning about a failure to extract the CISCO.CloudMode.1.0.zip archive. If the CISCO.CloudMode.1.0 device package was deleted, it will not be restored on import.

3.1(1i) and later

CSCvh02537

The IpCktEp policy might not be propagated to the leaf switch even after the policy has been configured properly on the Cisco APIC.

3.1(1i) and later

CSCvh07062

There will be fault in the Cisco APIC  for a remote leaf switch after upgrading the Cisco APIC upgrade or decommissioning and recommissioning the Cisco APIC.

3.1(1i) and later

CSCvh07996

There are duplicate CoPP rules in the TCAM.

3.1(1i) and later

CSCvh08044

In the case where the user posts policies to download a specific image version and also to upgrade to that version in quick succession before waiting for the image to get downloaded, the current running catalog gets picked up for checking the compatibility. In the event where the current running catalog does not support the newly requested version of the image, the upgrade will fail with the message "version not compatible," even though the user would expect compatibility.

3.1(1i) and later

CSCvh12315

The Cisco APIC will not allow the deletion of a remote leaf switch or POD TEP pool if there are any dhcpClient managed objects present with an IP address that is assigned from that TEP pool.

3.1(1i) and later

CSCvh13127

There is an issue with upgrading in the following situation:

■      A node is decommissioned a few hours before initiating an upgrade.

■      An upgrade is triggered with the "doNotPause" flag turned on in the maintenance group.

■      The node is in the maintenance group that is being upgraded.

In this situation, the upgrade stalls while waiting for that node to complete the upgrade.

3.1(1i) and later

CSCvh17075

If many unreachable stats export destinations are configured, the observer element on a switch might dump a core and restart.

3.1(1i) and later

CSCvh17321

On decommissioning and recomissioning of the Cisco APICs or nodes, extra prefix white list entries might be created on the TOR switches.

3.1(1i) and later

CSCvh18069

An iACL entry with a subnet mask of 0 or 32 is not allowed in the CoPP Pre-Filter creation wizard in the GUI.

3.1(1i) and later

CSCvh52046

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

3.1(1i) and later

CSCvh59843

Enabling Multicast under the VRF on one or more bridge domains is difficult due to how the drop-down menu is designed. This is an enhancement request to make the drop-down menu searchable.

3.1(1i) and later

CSCvi41092

The APIC log files are extremely large, which takes a considerable amount of time to upload, especially for users with slow internet connectivity.

3.1(1i) and later

CSCvi82903

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

3.1(1i) and later

CSCvj75897

A fault is raised that specifies problem that occurred while retrieving tagging information for a VMM controller.

Inventory pull from the VMware vCenter takes a long time (>10 minutes) and it continuously completes with a partial inventory result.

The processing of events from VMware vCenter is delayed, which may result in delays for the downloading of policies to the leaf switches when EPGs are deployed on-demand at the VMM domain. This would affect connectivity for newly deployed VMs or VMs which have been vMotioned.

3.1(1i) and later

CSCvj76503

A maintenance window triggered for an upgrade remains active for an unlimited time. Adding another node to this maintenance window automatically upgrades this newly added node. In some releases, such as 3.1(1i), a message may say that the window is triggered from X to Y time period; however, the maintenance window is still active for an unlimited time.

3.1(1i) and later

CSCvn00576

An SHA2 CSR for the ACI HTTPS certificate cannot be configured in the APIC GUI.

3.1(1i) and later

CSCvn15374

When upgrading Cisco APICs, constant heartbeat loss is seen, which causes the Cisco APICs to lose connectivity between one another. In the Cisco APIC appliance_director logs, the following message is seen several hundred times during the upgrade:

appliance_director||DBG4||...||Lost heartbeat from appliance id= ...

appliance_director||DBG4||...||Appliance has become unavailable id= ...

On the switches, each process (such as policy-element) see rapidly changing leader elections and minority states:

adrs_rv||DBG4||||Updated leader election on replica=(6,26,1)

3.1(1i) and later

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.1(1i) and later

CSCvp72283

An APIC running the 3.0(1k) release sometimes enters the "Data Layer Partially Diverged" state. The acidiag rvread command shows the following output for the service 10 (observer):

Non optimal leader for shards :10:1,10:3,10:4,10:6,10:7,10:9,10:10,10:12,10:13,10:15,10:16,10:18,10:19,10:21,10:22,10:24,10:25,

10:27,10:28,10:30,10:31

3.1(1i) and later

CSCvq43101

When opening an external subnet, a user cannot see Aggregate Export/Import check boxes set in GUI even though they were already configured.

3.1(1i) and later

CSCvq86573

Under a corner case, the Cisco APIC cluster DB may become partially diverged after upgrading to a release that introduces new services. A new release that introduces a new DME service (such as the domainmgr in the 2.3 release) could fail to receive the full size shard vector update in first two-minute window, which causes the new service flag file to be removed before all local leader shards are able to boot into the green field mode. This results in the Cisco APIC cluster DB becoming partially diverged.

3.1(1i) and later

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.1(1i) and later

CSCvr94614

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

3.1(1i) 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.1(1i) and later

CSCvw33061

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

3.1(1i) and later

CSCvf92483

This issue occurs while using the import-config file command on the CLI where the file is the output of export-config command. The file contains the output of show running-config of the scope where export-config was executed. The error occurs only when the file contains crypto commands, the bash shell throws the error and hangs without returning the prompt.

3.1.(1i)

CSCvg02551

When the IS-IS to OSPF Multi-Site CPTEP route leaking is not programmed, inter-site BGP session might go down on the spine switch. This behavior might cause traffic drop.

3.1.(1i)

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.1(1i) and later

CSCuo79243

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

3.1(1i) and later

CSCuo79250

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

3.1(1i) 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.1(1i) and later

CSCup79002

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

3.1(1i) and later

CSCuq21360

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

3.1(1i) 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.1(1i) 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.1(1i) 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.1(1i) and later

CSCut51929

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

3.1(1i) 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.1(1i) and later

CSCuu61998

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

3.1(1i) and later

CSCuu64219

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

3.1(1i) and later

CSCuw81638

The OpenStack metadata feature cannot be used with Cisco ACI integration with the Juno release (or earlier) of OpenStack due to limitations with both OpenStack and Cisco’s ML2 driver.

3.1(1i) and later

CSCva32534

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

3.1(1i) 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.1(1i) 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.1(1i) 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.1(1i) 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.1(1i) and later

CSCvg79127

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

3.1(1i) and later

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