Cisco Application Policy Infrastructure Controller, Release 2.2(3), Release Notes
Available Languages
Cisco Application Policy Infrastructure Controller Release Notes, Release 2.2(3)
This document describes the features, bugs, and limitations for the Cisco Application Policy Infrastructure Controller (APIC) software.
Note: Use this document in combination with the Cisco Nexus 9000 ACI-Mode Switches Release Notes, Release 12.2(3), which you can view at the following location:
Additional product documentation is listed in the "Related Documentation" section. Release notes are sometimes updated with new information about restrictions and bugs. See the following website for the most recent version of this document:
You can watch videos that demonstrate how to perform specific tasks in the Cisco APIC on the Cisco ACI YouTube channel:
https://www.youtube.com/c/CiscoACIchannel
Table 1 shows the online change history for this document.
Table 1 Online History Change
| Date |
Description |
| September 7, 2017 |
2.2(3j): Release 2.2(3j) became available. |
| November 13, 2017 |
2.2(3p): Release 2.2(3p) became available. Added the resolved bugs for this release. |
| November 20, 2017 |
In the Usage Guidelines section, changed a mention of "Virtual Private Cloud (VPC)" to "virtual port channel (vPC)." |
| December 2, 2017 |
2.2(3r): Release 2.2(3r) became available. Added the resolved bugs for this release. |
| December 21, 2017 |
2.2(3s): Release 2.2(3s) became available. Added the resolved bugs for this release. |
| January 25, 2018 |
In the Usage Guidelines section, removed a reference to VMware vCenter 6.5, as it is not supported in this release. |
| January 31, 2018 |
Readded the reference to VMware vCenter 6.5 that was removed on January 25, 2018. VMware vCenter 6.5 is now supported. |
| February 19, 2018 |
2.2(3t): Release 2.2(3t) became available; there are no changes to this document for this release. |
| February 21, 2018 |
2.2(3t): In the Resolved Bugs section, added bug CSCvg33397. |
| March 30, 2018 |
In the Compatibilty Information section, changed the supported Cisco AVS release to 5.2(1)SV3(3.3) and the VMM Integration and VMware Distributed Virtual Switch (DVS) release to 6.5. |
| November 21, 2018 |
2.2(3j): In the Open Bugs section, added bug CSCvn15374. |
| September 17, 2019 |
2.2(3j): In the Open Bugs section, added bug CSCuu17314 and CSCve84297. |
| 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. |
Contents
This document includes the following sections:
■ Bugs
Introduction
The Cisco Application Centric Infrastructure (ACI) is an architecture that allows the application to define the networking requirements in a programmatic way. This architecture simplifies, optimizes, and accelerates the entire application deployment life cycle.
The Ciscof Application Centric Infrastructure Fundamentals Guide provides complete details about the Cisco ACI, including a glossary of terms that are used in the Cisco ACI.
Compatibility Information
This release supports the following Cisco APIC servers:
| 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-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) |
The following list includes general compatibility information:
■ This release supports the hardware and software listed on the ACI Ecosystem Compatibility List document and the software listed as follows:
— Cisco NX-OS Release 12.2(3)
— Cisco AVS, Release 5.2(1)SV3(3.3)
For more information about the supported AVS releases, see the AVS software compatibility information in the Cisco Application Virtual Switch Release Notes at the following URL:
— Cisco UCS Manager software release 2.2(1c) or later is required for the Cisco UCS Fabric Interconnect and other components, including the BIOS, CIMC, and the adapter
See the ACI Ecosystem Compatibility List document at the following URL:
■ 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 ACI leaf switches
— Break out the 40G FEX ports on the N2348UPQ to 4x10G ports and connect to the 10G ports on all other ACI leaf switches
Note: A fabric uplink port cannot be used as a FEX fabric port.
■ Connecting the APIC (the controller cluster) to the ACI fabric requires a 10G interface on the ACI leaf switch. You cannot connect the APIC directly to the N9332PQ ACI leaf switch, unless you use a 40G to 10G converter (part number CVR-QSFP-SFP10G), in which case the port on the N9332PQ switch will auto-negotiate to 10G without requiring any manual configuration.
■ This release supports the following firmware:
— 2.0(3i) CIMC HUU iso
— 2.0(9c) CIMC HUU iso
— 2.0(13i) CIMC HUU iso (recommended)
■ For a table that shows the supported virtualization products, see the ACI Virtualization Compatibility Matrix at the following URL:
■ Beginning with Cisco Application Virtual Switch (AVS) release 5.2(1)SV3(1.10), you can connect service virtual machines that are part of Layer 4 to Layer 7 service graphs to AVS. Layer 4 to Layer 7 service graphs for Cisco AVS can be configured for service virtual machines that are in VLAN mode. By using an AVS VMM domain with both VLAN and VXLAN, you can have a virtual machine in VXLAN mode that is protected by service graphs that are using the service virtual machine in VLAN mode.
■ This release supports VMM Integration and VMware Distributed Virtual Switch (DVS) 6.5. For more information about guidelines for upgrading VMware DVS from 5.x to 6.x and VMM integration, see the Cisco ACI Virtualization Guide, Release 2.2(2) (this document also applies to the 2.2(3) release) at the following URL:
■ This release supports the Microsoft System Center Virtual Machine Manager (SCVMM) Update Rollup 9, 10, and 11 releases, and the Microsoft Windows Azure Pack Update Rollup 9, 10, and 11 releases.
■ This release supports SCVMM 2016 and Microsoft Hyper-V 2016.
■ This release supports the partner packages specified in the L4-L7 Compatibility List Solution Overview document at the following URL:
https://www.cisco.com/c/en/us/solutions/data-center-virtualization/application-centric-infrastructure/solution-overview-listing.html
■ This release supports Adaptive Security Appliance (ASA) device package version 1.2.5.5 or later.
■ If you are running a Cisco Adaptive Security Virtual Appliance (ASAv) version that is prior to version 9.3(2), you must configure SSL encryption as follows:
(config)# ssl encryption aes128-sha1
■ A known issue exists with the Safari browser and unsigned certificates, which applies when connecting to the APIC GUI. For more information, see the Cisco APIC Getting Started Guide.
■ For information about Cisco APIC compatibility with UCS Director, see the appropriate Cisco UCS Director Compatibility Matrix document at the following URL:
■ Beginning with this release, contracts using matchDscp filters are only supported on switches with "EX" on the end of the switch name. For example, N9K-93108TC-EX.
■ When downgrading from Cisco APIC 2.2(3) to an older release, if you need to delete the Virtual Port Channel (VPC), upgrade to Cisco APIC 2.2(3), delete the VPC, and downgrade again.
Usage Guidelines
This section lists usage guidelines for the Cisco APIC software.
■ The Cisco APIC GUI includes an online version of the Quick Start guide that includes video demonstrations.
■ The infrastructure IP address range must not overlap with other IP addresses used in the fabric for in-band and out-of-band networks.
■ The Cisco APIC does not provide IPAM services for tenant workloads.
■ To reach the Cisco APIC CLI from the GUI: select System > Controllers, highlight a controller, right-click and select "launch SSH". To get the list of commands, press the escape key twice.
■ In some of the 5-minute statistics data, the count of ten-second samples is 29 instead of 30.
■ For the following services, use a DNS-based host name with out-of-band management connectivity. IP addresses can be used with both in-band and out-of-band management connectivity.
— Syslog server
— Call Home SMTP server
— Tech support export server
— Configuration export server
— Statistics export server
■ Both leaf and spine switches can be managed from any host that has IP connectivity to the fabric.
■ If an IP address is learned on one of two endpoints for which you are configuring an atomic counter policy, you should use an IP-based policy and not a client endpoint-based policy.
■ When configuring two Layer 3 external networks on the same node, the loopbacks need to be configured separately for both Layer 3 networks.
■ All endpoint groups (EPGs), including application EPGs and Layer 3 external EPGs, require a domain. Interface policy groups must also be associated with an Attach Entity Profile (AEP), and the AEP must be associated with domains. Based on the association of EPGs to domains and of the interface policy groups to domains, the ports and VLANs that the EPG uses are validated. This applies to all EPGs including bridged Layer 2 outside and routed Layer 3 outside EPGs. For more information, see the Cisco APIC Layer 2 Networking Configuration Guide.
Note: When creating static paths for application EPGs or Layer 2/Layer 3 outside EPGs, the physical domain is not required. Upgrading without the physical domain will raise a fault on the EPG stating "invalid path configuration."
■ An EPG can only associate with a contract interface in its own tenant.
■ User passwords must meet the following criteria:
— Minimum length is 8 characters
— Maximum length is 64 characters
— Fewer than three consecutive repeated characters
— At least three of the following character types: lowercase, uppercase, digit, symbol
— Cannot be easily guessed
— Cannot be the username or the reverse of the username
— Cannot be any variation of "cisco", "isco", or any permutation of these characters or variants obtained by changing the capitalization of letters therein
■ The power consumption statistics are not shown on leaf node slot 1. You must view the statistics from any other node.
■ For Layer 3 external networks created through the API or Advanced GUI and updated through the CLI, protocols need to be enabled globally on the external network through the API or Advanced GUI, and the node profile for all the participating nodes needs to be added through the API or Advanced GUI before doing any further updates through the CLI.
■ For Layer 3 external networks created through the Basic GUI or CLI, you do not update them through the API. These external networks are identified by names starting with "__ui_".
■ The output from show commands issued in the NX-OS-style CLI are subject to change in future software releases. Cisco does not recommend using the output from the show commands for automation.
■ The CLI is supported only for users with administrative login privileges.
■ Do not separate virtual port channel (vPC) member nodes into different configuration zones. If the nodes are in different configuration zones, then the vPCs’ modes become mismatched if the interface policies are modified and deployed to only one of the vPC member nodes.
■ If you defined multiple login domains, you can choose the login domain that you want to use when logging in to a Cisco APIC. By default, the domain drop-down list is empty, and if you do not choose a domain, the DefaultAuth domain is used for authentication. This can result in login failure if the username is not in the DefaultAuth login domain. As such, you must enter the credentials based on the chosen login domain.
■ A firmware maintenance group should contain a maximum of 80 nodes.
■ When contracts are not associated with an endpoint group, DSCP marking is not supported for a VRF with a vzAny contract. DSCP is sent to a leaf switch along with the actrl rule, but a vzAny contract does not have an actrl rule. Therefore, the DSCP value cannot be sent.
■ When creating a vPC domain between two leaf switches, both switches must be in the same switch generation. Switches not in the same generation are not compatible vPC peers. The generations are as follows:
— Generation 1—Cisco Nexus N9000K switches without "EX" on the end of the switch name; for example, N9K-9312TX
— Generation 2—Cisco Nexus N9K switches with "EX" on the end of the switch model name; for example, N9K-93108TC-EX
■ Cisco ACI does not support a class E address as a VTEP address.
■ In a multipod fabric, if a spine switch in POD1 uses the infra tenant L3extOut-1, the TORs of the other pods (POD2, POD3) cannot use the same infra L3extOut (L3extOut-1) for Layer 3 EVPN control plane connectivity. Each POD must use its own spine switch and infra L3extOut.
■ A multipod deployment requires the 239.255.255.240 system Global IP Outside (GIPo) to be configured on the inter-pod network (IPN) as a PIM BIDIR range. This 239.255.255.240 PIM BIDIR range configuration on the IPN devices can be avoided by using the Infra GIPo as System GIPo feature. The Infra GIPo as System GIPo feature must be enabled only after upgrading all of the switches in the ACI fabric, including the leaf switches and spine switches, to the latest APIC release.
■ In a multipod fabric setup, if a new spine switch is added to a pod, it must first be connected to at least one leaf switch in the pod. Then the spine switch will be able to discover and join the fabric.
■ The APICs must have 1 SSD and 2 HDDs, and both RAID volumes must be healthy before upgrading to this release. The APIC will not boot if the SSD is not installed.
■ You do not need to create a customized monitoring policy for each tenant. By default, a tenant shares the common policy under tenant common. The APIC automatically creates a default monitoring policy and enables common observables. You can modify the default policy under tenant common based on the requirements of your fabric.
■ If the communication between the APIC and vCenter is impaired, some functionality is adversely affected. The APIC relies on the pulling of inventory information, updating vDS configuration, and receiving event notifications from the vCenter for performing certain operations.
■ If you are upgrading VMware vCenter 6.0 to vCenter 6.5, you should first delete the following folder on the VMware vCenter:
C:\ProgramData\cisco_aci_plugin
If you do not delete the folder and you try to register a fabric again after the upgrade, you will see the following error message:
Error while saving setting in C:\ProgramData\cisco_aci_plugin\<user>_<domain>.properties
user is the user that is currently logged in to the vSphere Web Client, and domain is the domain to which the user belongs. Although you can still register a fabric, you do not have permissions to override settings that were created in the old VMware vCenter. You must enter any changes in the APIC configuration again after restarting VMware vCenter.
■ Caution: If you install 1 Gigabit Ethernet (GE) or 10GE links between the leaf and spine switches in the fabric, there is risk of packets being dropped instead of forwarded, because of inadequate bandwidth. To avoid the risk, use 40GE or 100GE links between the leaf and spine switches.
■ 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.
■ Limiting, Disabling, or Checking IP Learning: in Cisco APIC, you can configure the following options related to IP learning:
| IP Learning Option |
Location |
Application |
| Limit IP Learning to Subnet |
Tenants > tenant-name > Navigation > Bridge Domain > Bridge Domain name > Subnets > Create Subnet |
When this option is enabled, IP address learning is limited to the bridge domain subnets only. Every bridge domain can have multiple subnets associated with it. By default, all IP addresses are learned. |
| Enforce Subnet Check |
Fabric > Access Policies > Global Policies > Fabric Wide Setting Policy > Enforce Subnet Check |
Fabric wide, this applies to all leaf switches. When this knob is enabled, it effectively turns on subnet check on every Bridge Domain, regardless of the setting "Limit IP learning to Subnet" on each Bridge Domain. |
| Disable Remote EP Learn |
Fabric > Access Policies > Global Policies > Fabric Wide Setting Policy > Disable Remote EP Learn |
Fabric wide, this applies only on border leaf switches with at least one external bridge domain programmed. |
Verified Scalability Limits
For the verified scalability limits (except the CLI limits), see the Verified Scalability Guide for this release.
For the CLI verified scalability limits, see the Cisco NX-OS Style Command-Line Interface Configuration Guide for this release.
You can access these documents from the following website:
https://www.cisco.com/c/en/us/support/cloud-systems-management/application-policy-infrastructure-controller-apic/tsd-products-support-series-home.html
New and Changed Information
This section lists the new and changed features in this release and includes the following topics:
New Software Features
Table 2 lists the new software features in this release:
Table 2 New Software Features, Guidelines, and Restrictions
| Feature |
Description |
Guidelines and Restrictions |
| SVI Auto State
|
The default auto state behavior for SVI in Cisco APIC is that the SVI remains in the up state when the auto state value is disabled. This means that the SVI remains active even if no interfaces are operational in the corresponding VLANs. If the SVI auto state value is changed to enabled, then the SVI state depends on the port members in the associated VLANs. When a VLAN interface has multiple ports in the VLAN, the SVI goes to the down state when all of the ports in the VLAN go down. |
None. |
| Policy-Based Redirect and Tracking Service Nodes |
Policy-based redirect (PBR) feature now supports tracking service nodes. Both IPv4 and IPv6 addresses can be configured at the same time. |
None. |
| IP SLA Monitoring |
Switches internally use the Cisco IP SLA monitoring feature to support PBR tracking. |
None. |
New Hardware Features
For new hardware features, see the Cisco Nexus 9000 ACI-Mode Switches Release Notes, Release 12.2(3) at the following location:
Changes in Behavior
The following are changes in behavior for this release:
■ No routes are installed in the routing information base (RIB) when Border Gateway Protocol (BGP) administrative distance is set to 255.
Bugs
This section contains lists of open and resolved bugs and known behaviors.
Open Bugs
This section lists the open bugs. Click the bug ID to access the Bug Search tool and see additional information about the bug. The "Exists In" column of the table specifies the 2.2(3) releases in which the bug exists. A bug might also exist in releases other than the 2.2(3) releases.
Table 3 Open Bugs in the 2.2(3) Release
| Bug ID |
Description |
Exists in |
| When authenticating with the Cisco APIC using ISE (TACACS), all logins over 31 characters fail. |
2.2(3p) and later |
|
| CDP is not enabled on the management interfaces for the leaf switches and spine switches. |
2.2(3j) and later |
|
| The stats for a given leaf switch rule cannot be viewed if a rule is double-clicked. |
2.2(3j) and later |
|
| 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. |
2.2(3j) and later |
|
| A service cannot be reached by using the APIC out-of-band management that exists within the 172.17.0.0/16 subnet. |
2.2(3j) and later |
|
| 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] |
2.2(3j) and later |
|
| 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) |
2.2(3j) and later |
|
| 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 |
2.2(3j) and later |
|
| Cisco APIC might not be reachable on its IPv6 Out-of-Band (OOB) address from hosts that are not in the same subnet as Cisco APIC when OOB management IPv6 contracts are configured. |
2.2(3j) |
Resolved Bugs
This section lists the resolved bugs. Click the bug ID to access the Bug Search tool and see additional information about the bug. The "Fixed In" column of the table specifies whether the bug was resolved in the base release or a patch release.
Table 3 Resolved Bugs in the 2.2(3) Release
| Bug ID |
Description |
Fixed in |
| In a shared service scenario, routes are leaked from the Layer 3 Outside (L3Out) on VRF2 into VRF1 through a contract between an application EPG/External Layer 3 (l3extInstP) EPG on VRF1 and an external Layer 3 (l3extInstP) on VRF2. When removing contracts, L3Out VRF2 routes might not be withdrawn from VRF1. |
2.2(3j) |
|
| Policy-based redirect (PBR) might be stuck in the "applying" state when in multi-node deployment due to vnsAdjacencyDefCont duplication. |
2.2(3j) |
|
| Virtual Machine (VM) statistics might display the message "No stats data to display" in the Cisco APIC GUI. |
2.2(3j) |
|
| After changing the looseNode (any switch connected between the Cisco ACI fabric and servers in a VMM domain) address, endpoint groups (EPGs) might be removed from the leaf switch. |
2.2(3j) |
|
| When the Out-of-Band (OOB) management VLAN used by the Cisco APIC to connect to the vCenter is removed from the upstream switch, the change causes VMM domain connectivity loss. If the Cisco APIC has its OOB management VLAN suspended, the Cisco APIC is the VMM leader. Once the leader is disconnected, the followers cannot process events and continue sending sync requests. Once the event listener is started again, it must process thousands of events. Due to the high volume of events, the event listener might lock up and might get blocked. |
2.2(3j) |
|
| The VMM mgr process might crash repeatedly after connecting to the VMware vCenter for Virtual Distributed Switch (vDS) configuration. |
2.2(3j) |
|
| In a Cisco ACI with Microsoft SCVMM integration environment where the ApicScvmmService agent is installed on the SCVMM server, the ApicScvmmService agent might hang. |
2.2(3j) |
|
| The Cisco ACI with Microsoft SCVMM agent cannot be installed when an Active Directory (AD) generated user certificate exists on Windows 2016. |
2.2(3j) |
|
| The Cisco ACI with Microsoft SCVMM integration agent version 2.0(1q) might restart multiple times per day. |
2.2(3j) |
|
| Large endpoint processing churn might occur when running vMotion. |
2.2(3j) |
|
| A leaf switch might report being in discovery, and show commands that rely on the APIs might fail with a stack traceback of "No space left on device." |
2.2(3j) |
|
| The Cisco APIC GUI might not validate a subnet that has an IPv6 address with "/53" as a subnet mask. |
2.2(3j) |
|
| After replacing a leaf switch that is part of a Cisco ACI fabric, the new switch's serial number might not be visible on other switches in the fabric. |
2.2(3j) |
|
| An EPG might not appear once deployed on a selected port. |
2.2(3j) |
|
| The "Encap-already-in-use" fault might be raised by the policy element process running on a leaf switch. |
2.2(3j) |
|
| A Windows Azure Pack subscription enters the Out-of-Sync state when an admin attempts to suspend the subscription or activate a suspended subscription. |
2.2(3p) |
|
| SSH failures for the admin account from 127.0.0.1 are seen every 10 minutes against leaf and spine switches in the fabric. |
2.2(3p) |
|
| When using Microsoft Windows Azure Pack (WAP) Integration with Cisco ACI, accessing the tenant portal usage page through the My Account > Subscription ID > Networking (ACI) navigation path causes the following error to display: Failed to retrieve usage summary information from the service. |
2.2(3p) |
|
| Only VRF instances without periods are allowed to be used if you are planning on using vsh CLI commands that involve the VRF instances name. |
2.2(3p) |
|
| Cisco APIC might not be reachable on its IPv6 Out-of-Band (OOB) address from hosts that are not in the same subnet as Cisco APIC when OOB management IPv6 contracts are configured. |
2.2(3p) |
|
| In the Microsoft Windows Azure Pack (WAP) GUI, in the admin portal, in the Plan -> Networking (ACI) section, if you create and save the plan, then all available services are checked by default. In the tenant portal, if the plan only has one shared service, this is not an issue as there is no doubt as to which services are available. The tenant can be confused as to which service is available when there are two or more shared services marked. When checking the Cisco APIC GUI to investigate the if the shared services were actually created, there are no abnormal findings regarding the intended configuration. The imported contracts of the consumer tenants will be created after WAP tenants have checked and applied the shared service in the tenant portal, as per the normal workflow. |
2.2(3p) |
|
| If SCVMM loses communication with the DNS server, the Cisco APIC Agent Service cannot resolve the fully qualified domain name of the VMM cluster host name and the Cisco APIC Agent Service starts to delete the vmmDomain and logical network. Also, the PS command fails to delete the logical network, but the logical network gets deleted on SCVMM without any change in the Cisco APIC. |
2.2(3p) |
|
| The warning message is incorrect when a user decommissions a Cisco APIC. |
2.2(3p) |
|
| With SCVMM integration, when creating a network from the Windows Azure Pack portal, the port reports an error message similar to the following example: network name is too long, use a shorter network name The network fails to be created and no endpoint group is programmed in the Cisco APIC. |
2.2(3p) |
|
| The Cisco APIC PSU Operational Status is not updated correctly. |
2.2(3r) |
|
| There is a memory leak on leaf switches that causes device instability and reloads. |
2.2(3r) |
|
| There are out of memory failures for NX-OS Processes such as BGP. |
2.2(3r) |
|
| The show vlan-domain commands fails when the VLAN domain is configured on a vPC. |
2.2(3r) |
|
| The observer element process crashes multiple times on a leaf switch and does not restart after the last crash. |
2.2(3r) |
|
| The VMMMgr process crashes shortly after being started. |
2.2(3s) |
|
| All ESXi hosts show as disconnected under the VMM Integration when you click on the VMM domain. The VMware vCenter might still show as online. The svc_ifc_opflexelem.log file for the leaf switches will show DVS as not found. |
2.2(3s) |
|
| A standby Cisco APIC fails to replace an active Cisco APIC. |
2.2(3t) |
Known Behaviors
This section lists bugs that describe known behaviors. Click the Bug ID to access the Bug Search Tool and see additional information about the bug. The "Exists In" column of the table specifies the 3.0(1) releases in which the known behavior exists. A bug might also exist in releases other than the 2.2(3) releases.
Table 7 Known Behaviors in the 2.2(3) Release
| Bug ID |
Description |
Exists in |
| 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. |
2.2(3j) and later |
|
| In some of the 5-minute statistics data, the count of ten-second samples is 29 instead of 30. |
2.2(3j) and later |
|
| The node ID policy can be replicated from an old appliance that is decommissioned when it joins a cluster. |
2.2(3j) and later |
|
| The DSCP value specified on an external endpoint group does not take effect on the filter rules on the leaf switch. |
2.2(3j) and later |
|
| The hostname resolution of the syslog server fails on leaf and spine switches over in-band connectivity. |
2.2(3j) and later |
|
| Following a FEX or switch reload, configured interface tags are no longer configured correctly. |
2.2(3j) and later |
|
| Switches can be downgraded to a 1.0(1x) version if the imported configuration consists of a firmware policy with a desired version set to 1.0(1x). |
2.2(3j) and later |
|
| If the Cisco APIC is rebooted using the CIMC power reboot, the system enters into fsck due to a corrupted disk. |
2.2(3j) and later |
|
| 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. |
2.2(3j) and later |
|
| The traffic destined to a shared service provider endpoint group picks an incorrect class ID (PcTag) and gets dropped. |
2.2(3j) and later |
|
| 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. |
2.2(3j) and later |
|
| Newly added microsegment EPG configurations must be removed before downgrading to a software release that does not support it. |
2.2(3j) and later |
|
| Downgrading the fabric starting with the leaf switch will cause faults such as policy-deployment-failed with fault code F1371. |
2.2(3j) and later |
|
| Creating or deleting a fabricSetupP policy results in an inconsistent state. |
2.2(3j) and later |
|
| 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. |
2.2(3j) and later |
|
| 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. |
2.2(3j) and later |
|
| When downgrading from a 2.2(2e) release 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. |
2.2(3j) and later |
|
| No fault gets raised upon using the same encapsulation VLAN in a copy device in tenant common, even though a fault should get raised. |
2.2(3j) and later |
|
| Modifying DNS settings for the APIC does not update the DN settings inside the container for a stateful app. |
2.2(3j) and later |
|
| The Cisco APIC does not allow the underscore (or " _ ") symbol in the hostname as a valid character. |
2.2(3j) and later |
■ 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.
Related Documentation
The Cisco Application Policy Infrastructure Controller (APIC) documentation can be accessed from the following website:
The documentation includes installation, upgrade, configuration, programming, and troubleshooting guides, technical references, release notes, and knowledge base (KB) articles, as well as other documentation. KB articles provide information about a specific use case or a specific topic.
By using the "Choose a topic" and "Choose a document type" fields of the APIC documentation website, you can narrow down the displayed documentation list to make it easier to find the desired document.
The following list provides links to the release notes and verified scalability documentation:
■ Cisco ACI Simulator Release Notes
■ Cisco NX-OS Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches
■ Cisco Application Policy Infrastructure Controller OpenStack and Container Plugins Release Notes
■ Cisco Application Virtual Switch Release Notes
New Documentation
■ Cisco APIC Layer 4 to Layer 7 Services Deployment Guide, Release 2.2(3)
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2017-2018 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)