Cisco Application Policy Infrastructure Controller, Release 1.1(2i), Release Notes

 

This document describes the features, caveats, and limitations for the Cisco Application Policy Infrastructure Controller (APIC) software. For more information on specific hardware features, see the Cisco NX-OS Release 11.1(2i) Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches. Additional product documentation is listed in the “Related Documentation” section.

Release notes are sometimes updated with new information about restrictions and caveats. See the following website for the most recent version of this document:

https://www.cisco.com/c/en/us/support/cloud-systems-management/application-policy-infrastructure-controller-apic/tsd-products-support-series-home.html

Table 1 shows the online change history for this document.

Table 1 Online History Change

 

Contents

This document includes the following sections:

■        Introduction

■        Installation Notes

■        Upgrading the APIC Controller

■        Downgrading the APIC Controller

■        Compatibility Information

■        Usage Guidelines

■        Verified Scalability Limits

■        New and Changed Information

■        Caveats

■        Related Documentation

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 Cisco Application Centric Infrastructure Fundamentals guide provides complete details about the ACI, including a glossary of terms that are used in the ACI.

Installation Notes

■        For installation instructions, see the Cisco ACI Fabric Hardware Installation Guide.  

■        For instructions on how to access the APIC for the first time, see the Cisco APIC Getting Started Guide.

■        For the Cisco APIC Python SDK documentation, including installation instructions, see the Cisco APIC Python SDK Documentation.

■        Two installation egg files are needed for installation. You can download these files from a running APIC from the URLs below.

The following file is the SDK:

o    http[s]://<APIC address>/cobra/_downloads/acimodel-1.1_2i-py.egg

The following file includes the Python packages that model the Cisco ACI Management Information Tree:

o    http[s]://<APIC address>/cobra/_downloads/acicobra-1.1_2i-py2.7.egg

Note: Installation of the SDK with SSL support on Unix/Linux and Mac OS X requires a compiler. For a Windows installation, you can install the compiled shared objects for the SDK dependencies using wheel packages.

Note: The model package depends on the SDK package; be sure to install the SDK package first.

■        Cisco ACI with Microsoft System Center Virtual Machine Manager (SCVMM) or Microsoft Windows Azure Pack only supports ASCII characters. Non-ASCII characters are not supported. Ensure that English is set in the System Locale settings for Windows, otherwise ACI with SCVMM and Windows Azure Pack will not install. In addition, if the System Locale is later modified to a non-English Locale after the installation, the integration components might fail when communicating with the APIC and the ACI fabric.

You can find all of the indicated documentation at the following URL:

https://www.cisco.com/c/en/us/support/cloud-systems-management/application-policy-infrastructure-controller-apic/tsd-products-support-series-home.html

Upgrading the APIC Controller

Table 2 lists the supported APIC upgrades.

Table 2 Supported APIC Upgrades

Downgrading the APIC Controller

Downgrading from this release to 1.1(1o) or 1.0(4o) is supported. However, this release does not support a stateful downgrade to 1.0(3x) or earlier releases. If you wish to downgrade from this release to 1.0(3x) or earlier must perform a stateless downgrade, as shown in the following procedure.

Note: You must plan for a Fabric outage, as this procedure rebuilds the Fabric.

1         Export the Fabric configuration.

2         Run the “eraseconfig” command on the APIC controllers. This will reboot the controllers. Ensure that the controllers have been rebooted before moving on to step 3.

3         Run the “setup-clean-config.sh” script on the switch nodes and reload all of the switches. Steps 2 and 3 clear the configuration on the Fabric, making this is a stateless downgrade.

4         Rediscover the Fabric.

5         Downgrade the Fabric to the desired release.

6         Run the “eraseconfig setup” command on the APIC controllers. This step is required so that the script can run additional commands that might be required for the version that is being used. The “eraseconfig setup” command will reload the APICs.

7         Run the “setup-clean-config.sh” script on the switch nodes and reload them.

8         Complete the initial setup script on the APIC controllers.

9         Import the Fabric configuration using the import “merge” mode.

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 11.1(2i)

—      Cisco AVS, Release 5.2(1)SV3(1.5i)

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:

https://www.cisco.com/c/en/us/support/switches/application-virtual-switch/products-release-notes-list.html

—      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:

https://www.cisco.com/c/en/us/solutions/data-center-virtualization/application-centric-infrastructure/solution-overview-listing.html

■        The breakout of 40G ports to 4x10G on the N9332PQ switch is not supported in ACI-Mode.

■        To connect the N2348UPQ to ACI leaf switches, the following options are available:

—      Directly connect the 40G FEX ports on the N2348UPQ to the 40G switch ports on the N9332PQ switch

—      Break out the 40G FEX ports on the N2348UPQ to 4x10G ports and connect to the N9396PX or N9372PX switches

■        Connecting the APIC (the controller cluster) to the ACI fabric requires a 10G interface on the ACI leaf. You cannot connect the APIC directly to the N9332PQ ACI Leaf.

■        This release supports the following firmware:

—      1.5(4e) CIMC HUU iso

—      2.0(3i) CIMC HUU iso (recommended)

■        The Cisco Application Virtual Switch (AVS) in either VLAN or VXLAN mode is not supported with Layer 4 to Layer 7 service insertion or service chaining. VMware vSphere Distributed Switch (VDS) is the only supported configuration.

■        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.3.4.

■        For information about APIC compatibility with UCS Director, see the appropriate Cisco UCS Director Compatibility Matrix document at the following URL:

https://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-director/products-device-support-tables-list.html

Usage Guidelines

This section lists usage guidelines for the APIC software.

■        The APIC GUI supports the following browsers:

—      Chrome version 35 (at minimum) on Mac and Windows

—      Firefox version 26 (at minimum) on Mac, Linux, and Windows

—      Internet Explorer version 11 (at minimum)

—      Safari 7.0.3 (at minimum)

Note: Restart your browser after upgrading to release 1.1(2i).

Caution: A known issue exists with the Safari browser and unsigned certificates. Read the information presented here before accepting an unsigned certificate for use with WebSockets.

When you access the HTTPS site, the following message appears:

“Safari can’t verify the identity of the website APIC. The certificate for this website is invalid. You might be connecting to a website that is pretending to be an APIC, which could put your confidential information at risk. Would you like to connect to the website anyway?”

To ensure that WebSockets can connect, you must do the following:

1.        Click Show Certificate.

2.        choose Always Trust in the three drop-down lists that appear.

If you do not follow the steps above, WebSockets will not be able to connect.

■        The 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 APIC does not provide IPAM services for tenant workloads.

■        To reach the APIC CLI from the GUI: choose System > Controllers, highlight a controller, right-click and choose 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

■        In-band management connectivity to the spine switches is possible from any host that is connected to the leaf switches of the Fabric, and leaf switches can be managed from any host that has IP connectivity to the fabric.

■        When configuring an atomic counter policy between two endpoints, and an IP is learned on one of the two endpoints, it is recommended to 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 Fundamentals Guide and the KB: Creating Domains, Attach Entity Profiles, and VLANs to Deploy an EPG on a Specific Port article.

Note: In the 1.0(4x) and earlier releases, when creating static paths for application EPGs or Layer 2/Layer 3 outside EPGs, the physical domain was not required. In this release, it is 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.

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

Verified Scalability Limits

For the verified scalability limits, see the Verified Scalability Guide for this release:

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 Release 1.1(2i) and includes the following topics:

■        New Software Features

■        New Hardware Features

New Software Features

This release supports no new software features.

New Hardware Features

This release supports no new hardware features.

 

Caveats

This section contains lists of open and resolved caveats and known behaviors.

■        Open Caveats

■        Resolved Caveats

■        Known Behaviors

Open Caveats

Table 3 lists the open caveats in this release. Click the bug ID to access the Bug Search tool and see additional information about the bug.

Table 3 Open Caveats in Cisco APIC Release 1.1(2i)

Resolved Caveats

Table 4 lists the resolved caveats in this release. Click the bug ID to access the Bug Search tool and see additional information about the bug.

Table 4 Resolved Caveats in Cisco APIC Release 1.1(2i)

Known Behaviors

Table 5 lists caveats that describe known behaviors in the Cisco NX-OS Release 1.1(2i) release. Click the Bug ID to access the Bug Search Tool and see additional information about the bug.

Table 5 Known Behaviors in Cisco APIC Release 1.1(2i)

Related Documentation

The Cisco Application Policy Infrastructure Controller (APIC) documentation can be accessed 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

 

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.

© 2016-2017 Cisco Systems, Inc. All rights reserved.