Cisco NX-OS Release 11.0(4o) Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches
Available Languages
Cisco NX-OS Release 11.0(4o) Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches
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(4o), 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(4o) Release Notes for Cisco Nexus 9000 Series ACI-Mode Switches:
Table 1 shows the online change history for this document.
Table 1. Online History Change
| Date |
Description |
| June 25, 2015 |
Created the release notes for Release 11.0(4o) |
| July 8, 2015 |
Added B22 FEX models to the Supported FEX Models table. |
| December 9, 2015 |
Fixed incorrect URLs to the documentation on cisco.com. |
| March 1, 2016 |
In the Compatibility Information, fixed an incorrect reference to a leaf switch. |
Contents
This document includes the following sections:
■ Cisco Nexus 9000 Series ACI-Mode
■ Caveats
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.
| Hardware Type |
Product ID |
Description |
| Chassis |
N9K-C9504 |
Cisco Nexus 9504 chassis with four slots |
| Chassis |
N9K-C9508 |
Cisco Nexus 9508 chassis with 8 slots |
| Chassis component |
N9K-C9508-FAN |
Fan tray |
| Chassis component |
N9k-PAC-3000W-B |
Cisco Nexus 9500 3000W AC power supply, port side intake |
| Pluggable module (GEM) |
N9K-M6PQ |
6-port |
| Pluggable module (GEM) |
N9K-M12PQ |
12-port or 8-port |
| Spine switch |
N9K-C9336PQ |
Cisco Nexus 9336PQ switch, 36-port 40 Gigabit Ethernet QSFP |
| Spine switch |
N9K-C9508-B1 |
Cisco Nexus 9508 chassis bundle with 1 supervisor module, 3 power supplies, 2 system controllers, 3 fan trays, and 3 fabric modules |
| Spine switch |
N9K-C9508-B2 |
Cisco Nexus 9508 chassis bundle with 1 supervisor module, 3 power supplies, 2 system controllers, 3 fan trays, and 6 fabric modules |
| Spine switch fan |
N9K-C9300-FAN3 |
Port side intake fan |
| Spine switch fan |
N9K-C9300-FAN3-B |
Port side exhaust fan |
| Spine switch module |
N9K-C9504-FM |
Cisco Nexus 9504 fabric module |
| Spine switch module |
N9K-C9508-FM |
Fabric module |
| Spine switch module |
N9K-X9736PQ |
Cisco Nexus 9500 36-port, 40 Gigabit Ethernet QSFP aggregation module |
| Switch module |
N9K-SC-A |
Cisco Nexus 9500 Series system controller |
| Switch module |
N9K-SUP-A |
Cisco Nexus 9500 Series supervisor module |
| Switch module |
N9K-SUP-B |
Cisco Nexus 9500 Series supervisor module |
| Top-of-rack (ToR) leaf switch |
N9K-C93128TX |
Cisco Nexus 9300 96-port, 1-/10-Gbps BASE-T and 6-port or 8-port, 40 Gigabit Ethernet QSFP switch |
| Top-of-rack (ToR) leaf switch |
N9K-C9332PQ |
Cisco Nexus 9332PQ 32-port 40 Gigabit Ethernet QSFP+ Top-of-rack (ToR) Layer 3 switch |
| Top-of-rack (ToR) leaf switch |
N9K-C9372PX |
Cisco Nexus 9372PX 48-port, 10 Gigabit Ethernet SFP+ and 6-port 40 Gigabit Ethernet QSFP+ Top-of-rack (ToR) Layer 3 switch |
| Top-of-rack (ToR) leaf switch |
N9K-C9372TX |
Cisco Nexus 9372TX 48-port, 1/10 Gbps Base-T and 6-port, 40 Gigabit Ethernet QSFP Top-of-rack (ToR) Layer 3 switch |
| Top-of-rack (ToR) leaf switch |
N9K-C9396PX |
Cisco Nexus 9300 48-port, 1/10 Gigabit Ethernet SFP+ and 6-port or 12-port, 40 Gigabit Ethernet QSFP switch |
| Top-of-rack (ToR) leaf switch |
N9K-C9396TX |
Cisco Nexus 9300 48-port, 1/10 Gbps Base-T and 6-port or 12-port, 40 Gigabit Ethernet QSFP switch |
| Top-of-rack (ToR) leaf switch power supply unit |
UCSC-PSU-930WDC V01 |
Port side intake DC power supply compatible with all ToR leaf switches |
| Top-of-rack (ToR) leaf switch power supply unit |
N9K-PAC-650W-B |
650W AC Power supply, port side exhaust pluggable |
| Top-of-rack (ToR) leaf switch power supply unit |
N9K-PAC-650W |
650W AC Power supply, port side intake pluggable |
| Top-of-rack (ToR) leaf switch power supply unit |
N9K-PAC-1200W-B |
1200W AC Power supply, port side exhaust pluggable |
| Top-of-rack (ToR) leaf switch power supply unit |
N9K-PAC-1200W |
1200W AC Power supply, port side intake pluggable |
| Top-of-rack (ToR) leaf switch power supply unit |
N9K-PUV-3000W-B |
3000W AC Power supply, port side exhaust pluggable |
| Top-of-rack (ToR) leaf switch fan |
NXA-FAN-30CFM-F |
Port side exhaust fan |
| Top-of-rack (ToR) leaf switch fan |
NXA-FAN-30CFM-B |
Port side intake fan |
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.
| Product ID |
Description |
| N2K-B22DELL-P |
B22 FEX for Dell |
| N2K-B22IBM-P |
B22 FEX for IBM |
| N2K-C2248PQ-10GE |
Cisco Nexus 2248PQ 10GE Fabric Extender, 2PS, 4 Fan Module, 48x1/10GE (req SFP/SFP+) + 4x40G QSFP+(req QSFP+), choice of airflow and power supply |
| N2K-C2248TP-1GE |
Cisco Nexus 2248TP Series 1GE Fabric Extender, 2 AC PS, 1 Fan Module (Standard Airflow/port side exhaust), 48x100/1000Base-T + 4x10GE (req SFP+), same as N2K-C2248TP |
| N2K-C2248TP-E-1GE |
Cisco Nexus 2248TP-E Series 1GE Fabric Extender, 2PS, 1 Fan Module, 48x100/1000Base-T + 4x10GE (req SFP+), 32MB buffer, choice of airflow and power supply |
| N2K-C2232PP-10GE |
Cisco Nexus 2232PP Series 10GE Fabric Extender, 2 AC PS, 1 Fan Module (Standard Airflow/port side exhaust), 32x1/10GE (req SFP/SFP+) + 8x10GE (req SFP+), same as N2K-C2232PP |
| N2K-C2232TM-E-10GE |
Cisco Nexus 2232TM-E Series 10GBASE-T Fabric Extender, 2PS, 1 Fan Module, 32x1/10GBase-T + 8x10GE Module (req SFP+), choice of airflow and power supply |
Installation Notes
For installation instructions, see the Cisco ACI Fabric Hardware Installation Guide.
Compatibility Information
■ Cisco NX-OS Release 11.0(4o) 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
■ Leafs and spines from two different fabrics cannot be connected regardless of whether the links are administratively kept down.
Caveats
This section contains lists of open and resolved caveats and known behaviors.
Open Caveats
Table 4 lists the open caveats in the Cisco NX-OS Release 11.0(4o). 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(4o)
| Bug ID |
Description |
| FEX logs are missing in the output of the show fex detail command. |
|
| Events and faults for interfaces are not updated under Ports in the GUI. |
|
| The output of some CLI commands displays very slowly. |
|
| FEX related diagnostic results are missing. |
|
| The REST API on the CLI of the switch throws an error when trying to reload. |
|
| FEX support is not available when connected behind a N9K-C9332PQ ToR. |
Resolved Caveats
Table 5 lists the resolved caveats in the Cisco NX-OS Release 11.0(4o). 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(4o)
| Bug ID |
Description |
| The Logical Interface Profile configuration for SVI does not require the user to enter a subnet mask. |
|
| The command show endpoint vrf all does not provide a summary of all VRFs. |
|
| The EPMC process cores because of memory corruption in the EPMC process. |
|
| Endpoints are missing in the COOP repository on some or all of the spines, and the show coop internal info global command shows mismatched information on the spines. |
|
| When a MAC is moving continuously between multiple encap VLANs (aka EPGs) within the same BD, high CPU utilization leading to eventual policyelem cores on switch. |
|
| When enabling routing on a BD, existing endpoints will have the issue of not rewriting the source MAC on routing traffic. |
|
| Traffic loss and high CPU utilization can be seen in such cases as when having vrf-crossing configured only in one direction for shared-services. |
|
| When an endpoint (EP) with multiple IPs moves from an orphan port on one leaf switch to a FEX straight through vPC, traffic loss may occur for some IPs in that EP for ~3 minutes. |
|
| Sometimes on VM moves, due to RARP, traffic loss is occurs for 2-3 minutes. |
|
| ISIS packet drops in the spine and tunnels may go down. |
|
| The link on the border leaf takes a long time to come back up after reload operations. |
|
| When routing is disabled on the BD and unknown MAC unicast is set to porxy, traffic loss is seen on a leaf reload/vPC flap. |
|
| At least one of the following symptoms occurs: ■ show module is very slow or fails from vsh ■ PFM process crashes |
|
| ACI leafs drop ISIS hello packets when received from an endpoint group in a user tenant. |
|
| Traffic loss occurs between the fabric endpoints and layer 3 external network devices for some flows on ToRs with a policy CAM greater than 4k. |
|
| /var/sysmgr/ causes unrecoverable-error in fabric modules. |
|
| Connectivity to some nodes on In-band Management VRFs is sometimes lost., and commands such as ping and ssh will sometimes not work. Other VRFs are not affected. |
|
| SNA sessions will not establish between endpoints. |
|
| Some of the entries in TCAM tables are missing, and a few of them have incorrect data. |
|
| The ACI N9K switches use the router MAC as the source MAC address, which is all zeros, for sending CDP packets. When receiving CDP packets, most switches do not check the source MAC address to determine if the CDP packets should be dropped. |
|
| A fault appears in the APIC saying the /var/log partition is full. |
|
| On downgrading from a 1.1(1x) to a 1.0(4x) release, the vPC endpoints can be out of sync between the vPC pair of leaf switches; this results in traffic loss for all the vPC traffic destined to the vPC leaf switch that was downgraded. |
Known Behaviors
Table 6 lists caveats that describe known behaviors in the Cisco NX-OS Release 11.0(4o). 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(4o)
| Bug ID |
Description |
| Configuring the BGP maximum prefix policy is not supported. |
|
| Layer 3 switched packets that go out of a FEX Hif interface are not spanned. |
|
| When output span is enabled on a port where the filter is VLAN, multicast traffic in the VLAN that goes out of that port is not spanned. |
|
| Continuous “threshold exceeded” messages are generated from the fabric. |
|
| Switch rescue user ("admin") can log into fabric switches even when TACACS is selected as the default login realm. |
|
| An extra 4 bytes is added to the untagged packet with Egress local and remote SPAN. |
|
| When the command show ip ospf vrf <vrf_name> is run from bash on the border leaf, the checksum field in the output always shows a zero value. |
|
| When an IP moves from one MAC behind one ToR to another MAC behind another ToR, even though the VM sends a GARP packet, in ARP unicast mode, this GARP packet is not flooded. As a result, any other host with the original MAC to IP binding sending an L2 packet will send to the original ToR where the IP was in the beginning (based on MAC lookup), and the packet will be sent out on the old port (location). Without flooding the GARP packet in the network, all hosts will not update the MAC-to-IP binding. |
|
| When modifying the L2Unknown Unicast parameter on a Bridge Domain (BD), interfaces on externally connected devices may bounce. Additionally, the endpoint cache for the BD is flushed and all endpoints will have to be re-learned. |
|
| If an endpoint has multiple IPs, the endpoint will not be aged until all IPs go silent. If one of the IPs is reassigned to another server/host, the fabric detects it as an IP move and forwarding will work as expected. |
|
| The PSU is not getting detected after OIR with Power input connected. |
|
| iping picks a source address from a different subnet for a directly connected destination. |
|
| When a traceroute is performed from a VM attached to a regular bridge domain and to a VM behind a border leaf, and both of these VMs are behind two different ToRs, the traceroute does not show the ToR with the border leaf. |
|
| The port-channel remains in the admin-down state after being enabled. |
|
| The access-port operational status is trunk. |
|
| When removing the secondary IP on an external SVI interface, static routes defined in the VRF, or context of the SVI, are removed causing traffic to be looped in the fabric. |
|
| The output incorrectly displays AOC cables as ACU cables. |
|
| If the TOR 1RU system is configured with the RED fan (the reverse airflow), the air will flow from back to front. The temperature sensor in the back will be defined as an Inlet temperature sensor, and the temperature sensor in the front will be defined as an outlet temperature sensor. If the TOR 1RU system is configured with the BLUE fan (normal airflow), the air will flow from front to back. The temperature sensor in the front will be defined as an Inlet temperature sensor, and the temperature sensor in the back will be defined as outlet temperature sensor. From the airflow perspective, the Inlet sensor reading should always be less than the outlet sensor reading. However, in the TOR 1RU family, the front panel temperature sensor has some inaccurate readings due to the front panel utilization & configuration, which causes the Inlet temperature sensor reading to be very close, equal, or even greater than the outlet temperature reading. |
|
| 10% to 11% traffic drops occur on Unicast Traffic Streams. |
|
| Traffic from the orphan port to the vPC pair is not recorded against the tunnel stats. Traffic from the vPC pair to the orphan port is recorded against the tunnel stats. |
|
| Traffic from the orphan port to the vPC pair is only updated on the destination node, so the traffic count shows as excess. |
|
| On downgrading from a 1.1(1x) to a 1.0(4x) release with shared service configuration, depending on timing conditions, the traffic takes anywhere between 0-10 seconds to converge. |
■ 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
The Cisco Application Policy Infrastructure Controller (APIC) documentation can be accessed from this website:
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.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)