Cisco NX-OS Release 11.0(3k) Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches

 

First Published: April 3, 2015

 

This document describes the features, caveats, and limitations for Cisco NX-OS software that runs on Cisco Nexus 9000 Series Application Centric Infrastructure (ACI) switches. Use this document in combination with the Cisco Application Policy Infrastructure Controller, Release 1.0(3k), Release Notes. 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 the Cisco NX-OS Release 11.0(3k) Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-release-notes-list.html  

Table 1 shows the online change history for this document.

Table 1. Online History Change

 

Contents

This document includes the following sections:

■        Cisco Nexus 9000 Series ACI-Mode

■        Supported Hardware

■        Supported FEX Models

■        Installation Notes

■        Upgrade Instructions

■        Downgrade Instructions

■        Compatibility Information

■        Usage Guidelines

■        Caveats

■        Related Documentation

Cisco Nexus 9000 Series ACI-Mode

Cisco NX-OS Software for the Cisco Nexus 9000 Series is a data center, purpose-built, operating system designed with performance, resiliency, scalability, manageability, and programmability at its foundation. It provides a robust and comprehensive feature set that meets the requirements of virtualization and automation in data centers

Cisco NX-OS Release 11.0 works only on Cisco Nexus 9000 Series switches in ACI Mode.

See Table 2 for a list of modules that are supported on Cisco Nexus 9000 Series switches in ACI Mode.

Supported Hardware

Table 2 lists the hardware that the Cisco Nexus 9000 Series ACI Mode switches support.

Table 2. Cisco Nexus 9000 Series Hardware.

 

Supported FEX Models

Table 3 lists the FEX models that the Cisco Nexus 9000 Series ACI Mode switches support. For more information on the FEX models, see Cisco Nexus 2000 Series Fabric Extenders Data Sheet.

Note: FEX requires software version 5.x or later to be brought up successfully.

Table 3. Supported FEX Models.

Installation Notes

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

Upgrade Instructions

Follow this procedure when upgrading from a 1.0(2x) release to a 1.0(3x) release:

1.     Upgrade the APIC controller software image.

2.     After all APICs in the cluster are successfully upgraded, upgrade all the switches in the fabric.

Note: The switches may need to be rebooted after upgrading (See CSCut32029).

Downgrade Instructions

Follow this procedure when downgrading from a 1.0(3x) release to a 1.0(2x) release:

1.     Downgrade the APIC controller software image.

2.     After all APICs in the cluster are successfully downgraded, downgrade all the switches in the fabric.

Note: Switch models N9K-C9372PX, N9K-C9332PQ, and N9K-C9372TX are not supported for downgrading in the APIC 1.0(2x) or the Cisco Nexus 9000 11.0(2x) releases. If your fabric has those models, do not downgrade.

Compatibility Information

■        Cisco NX-OS Release 11.0(3k) supports the hardware and software listed on the ACI Ecosystem Compatibility List and the Cisco AVS, Release 4.2(1)SV2(2.3).

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

■        To connect the APIC (the controller cluster) to the ACI fabric, it is required to have a 10G interface on the ACI leaf. You cannot connect the APIC directly to the N9332PQ ACI spine.

Usage Guidelines

■        The current list of protocols that are allowed (and cannot be blocked through contracts) include the following. Some of the protocols have SrcPort/DstPort distinction.

Note: Also see the APIC release notes for policy information: https://www.cisco.com/c/en/us/support/cloud-systems-management/application-policy-infrastructure-controller-apic/tsd-products-support-series-home.html

—      UDP DestPort 161: SNMP. These cannot be blocked through contracts. Creating an SNMP ClientGroup with a list of Client-IP Addresses restricts SNMP access to only those configured Client-IP Addresses. If no Client-IP address is configured, SNMP packets are allowed from anywhere.

—      TCP SrcPort 179: BGP

—      TCP DstPort 179: BGP

—      OSPF

—      UDP DstPort 67: BOOTP/DHCP

—      UDP DstPort 68: BOOTP/DHCP

—      IGMP

—      PIM

—      UDP SrcPort 53: DNS replies

—      TCP SrcPort 25: SMTP replies

—      TCP DstPort 443: HTTPS

—      UDP SrcPort 123: NTP

—      UDP DstPort 123: NTP

Caveats

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

■        Open Caveats

■        Resolved Caveats

■        Known Behaviors

Open Caveats

Table 4 lists the open caveats in in the Cisco NX-OS Release 11.0(3k). Click the bug ID to access the Bug Search tool and see additional information about the bug.

Table 4. Open Caveats in Cisco NX-OS Release 11.0(3k)

Resolved Caveats

Table 5 lists the resolved caveats in the Cisco NX-OS Release 11.0(3k). Click a Bug ID to access the Bug Search Tool and see additional information about the bug

Table 5.  Resolved Caveats in Cisco NX-OS Release 11.0(3k)

Known Behaviors

Table 6 lists caveats that describe known behaviors in the Cisco NX-OS Release 11.0(3k). Click the Bug ID to access the Bug Search Tool and see additional information about the bug.

Table 6. Known Behaviors in Cisco NX-OS Release 11.0(3k)

 

■        The Cisco Nexus 9508 ACI-mode switch supports warm (stateless) standby where the state is not synched between the active and the standby supervisor modules. For an online insertion and removal (OIR) or reload of the active supervisor module, the standby supervisor module becomes active, but all modules in the switch are reset because the switchover is stateless. In the output of the show system redundancy status command, warm standby indicates stateless mode.

■        When a recommissioned APIC controller rejoins the cluster, GUI and CLI commands can time out while the cluster expands to include the recommissioned APIC controller.

■        If connectivity to the APIC cluster is lost while a switch is being decommissioned, the decommissioned switch may not complete a clean reboot. In this case, the fabric administrator should manually complete a clean reboot of the decommissioned switch.

■        Before expanding the APIC cluster with a recommissioned controller, remove any decommissioned switches from the fabric by powering down and disconnecting them. Doing so will ensure that the recommissioned APIC controller will not attempt to discover and recommission the switch.

IGMP Snooping Known Behaviors:

■        Multicast router functionality is not supported when IGMP queries are received with VxLAN encapsulation.

■        IGMP Querier election across multiple Endpoint Groups (EPGs) or Layer 2 outsides (External Bridged Network) in a given Bridge Domain (BD) is not supported. Only one EPG or Layer 2 outside for a given BD should be extended to multiple multicast routers if any.

■        The rate of the number of IGMP reports sent to a leaf switch should be limited to 1000 reports per second.

■        Unknown IP multicast packets are flooded on ingress leaf switches and border leaf switches, unless “unknown multicast flooding” is set to “Optimized Flood” in a BD. This knob can be set to “Optimized Flood” only for a maximum of 50 BDs per leaf.

If “Optimized Flood” is enabled for more than the supported number of BDs on a leaf, follow these configuration steps to recover:

—      Set “unknown multicast flooding” to “Flood” for all BDs mapped to a leaf.

—      Set “unknown multicast flooding” to “Optimized Flood” on needed BDs.

Related Documentation

This section lists the product documentation for the Cisco ACI.

Web-Based Documentation

■        Cisco APIC Management Information Model Reference

■        Cisco APIC Online Help Reference

■        Cisco ACI MIB Support List

■        Cisco 10-Gigabit Ethernet Transceiver Modules Compatibility Matrix:

https://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/10GE_Tx_Matrix.html

■        Cisco 40-Gigabit Ethernet Transceiver Modules Compatibility Matrix:

https://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/40GE_Tx_Matrix.html

Downloadable Documentation

■        Cisco ACI Fundamentals

■        Cisco APIC Getting Started Guide

■        Cisco APIC REST API User Guide

■        Cisco APIC Command Line Interface User Guide

■        Cisco ACI Switch CLI Command Reference, NX-OS Release 11.0

■        Cisco APIC Faults, Events, and Error Messages Guide

■        Cisco ACI System Messages Reference Guide

■        Cisco ACI Troubleshooting Guide

■        Cisco NX-OS to APIC Mapping Guide

■        Cisco APIC Layer 4 to Layer 7 Device Package Development Guide

■        Cisco APIC Layer 4 to Layer 7 Services Deployment Guide

■        Cisco AVS Configuration Guide

■        Cisco AVS Installation and Upgrade Guide

■        Cisco ACI MIB Quick Reference

■        Cisco ACI Fabric Hardware Installation Guide

■        Cisco ACI MIB Quick Reference

■        Cisco APIC Release Notes

■        Cisco Application Centric Infrastructure Release Notes

Hardware Documentation

■        Cisco Nexus 9336PQ ACI-Mode Switch Hardware Installation Guide

■        Cisco Nexus 9508 ACI-Mode Switch Hardware Installation Guide

This document is to be used in conjunction with the documents listed in the “Related Documentation” section.

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.

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