Cisco Nexus 9000 Series NX-OS Release Notes, Release 7.0(3)I4(2)

Cisco Nexus 9000 Series NX-OS Release Notes, Release 7.0(3)I4(2)

 

This document describes the features, caveats, and limitations for Cisco NX-OS Release 7.0(3)I4(2) software for use on the following switches:

■        Cisco Nexus 9000 Series

■        Cisco Nexus 31128PQ

■        Cisco Nexus 3164Q

■        Cisco Nexus 3232C

■        Cisco Nexus 3264Q

Use this document in combination with documents listed in Related Documentation.

 

Table 1 shows the online change history for this document.

Table 1 Online History Change

 

Contents

Introduction. 4

System Requirements. 4

New and Changed Information. 15

Caveats. 17

Upgrade and Downgrade. 21

Limitations. 21

Guidelines and Limitations for Private VLANs. 24

Unsupported Features. 28

Related Documentation. 32

Obtaining Documentation and Submitting a Service Request. 33

 

Introduction

Cisco NX-OS software is a data center-class operating system designed for performance, resiliency, scalability, manageability, and programmability at its foundation. The Cisco NX-OS software provides a robust and comprehensive feature set that meets the requirements of virtualization and automation in mission-critical data center environments. The modular design of the Cisco NX-OS operating system makes zero-impact operations a reality and enables exceptional operational flexibility.

The Cisco Nexus 9000 Series uses an enhanced version of Cisco NX-OS software with a single binary image that supports every switch in the series, which simplifies image management.

System Requirements

This section includes the following sections:

■        Supported Cisco Software Releases

■        Supported Device Hardware

■        Supported Optics

■        Supported FEX Modules

Supported Cisco Software Releases

Table 2 summarizes information about the Cisco Nexus platforms and software release versions that Cisco OpenFlow Plug-in supports.

Table 2 Cisco Plug-in for OpenFlow Compatibility Matrix

 

Supported Device Hardware

The tables below list the Cisco Nexus 9000 Series hardware that Cisco NX-OS Release 7.0(3)I4(1) supports. For additional information about the supported hardware, see the Hardware Installation Guide for your Cisco Nexus 9000 Series device.

■        Table 3 lists the Cisco Nexus 9000 Series fabric modules

■        Table 4 lists the Cisco Nexus 9000 Series fans and fan trays

■        Table 5 lists the Cisco Nexus 9000 Series line cards

■        Table 6 lists the Cisco Nexus 9000 Series power supplies

■        Table 7 lists the Cisco Nexus 9000 Series supervisor modules

■        Table 8 lists the Cisco Nexus 9000 Series system controllers

■        Table 9 lists the Cisco Nexus 9000 Series uplink modules

■        Table 11 lists the 3232C and 3264Q switch hardware

■        Table 12 lists the Cisco Nexus 3164Q switch hardware

■        Table 13 lists the Cisco Nexus 31128PQ switch hardware

Table 3 Cisco Nexus 9000 Series Fabric Modules

 

 

 

Table 4 Cisco Nexus 9000 Series Fans and Fan Trays

Table 5 Cisco Nexus 9500 Platform Line Cards

Table 6 Cisco Nexus 9000 Series Power Supplies

Table 7 Cisco Nexus 9500 platform Supervisor Modules

Table 8 Cisco Nexus 9000 Series Switches

Table 9 Cisco Nexus 9000 Series Uplink Modules

 

Table 10 Cisco Nexus 9500 platform System Controller

 

Table 11 Cisco Nexus 3232C and 3264Q Switch Hardware

Note: Beginning with Cisco NX-OS Release 7.0(3)I4(2), 25G CVR-2QSFP28-8SFP is supported on the Cisco Nexus 3232C switches.

 

Table 12 Cisco Nexus 3164Q Switch Hardware

 

 

Table 13 Cisco Nexus 31128PQ Switch Hardware

 

Note: The Cisco Nexus M6PQ-E uplink module and the Cisco Nexus 9372PX-E and 9372TX-E switches need to run the following minimum Cisco NX-OS releases:

·         7.0(3)I2(2d)

·         7.0(3)I2(2e)

·         7.0(3)I3(2)

·         7.0(3)I4(1)

Supported Optics

See the Cisco 10-Gigabit Ethernet Transceiver Modules Compatibility Matrix for a list of supported optical components.

Supported FEX Modules

Cisco NX-OS Release 7.0(3)I4(2) supports the following FEXes (Fabric extenders) on Cisco Nexus 9332PQ, 9372PX, 9372PX-E, 9396PX, and 9500 platform switches:

■        Cisco Nexus 2224TP

■        Cisco Nexus 2232PP

■        Cisco Nexus 2232TM and 2232TM-E

■        Cisco Nexus 2248PQ

■        Cisco Nexus 2248TP and 2248TP-E

■        Cisco Nexus 2348TQ

■        Cisco Nexus 2348UPQ

■        Cisco Nexus B22Dell

■        Cisco Nexus B22HP

■        Cisco Nexus NB22FTS

■        Cisco Nexus NB22IBM

Note: Cisco Nexus switches other than Cisco Nexus 9332PQ, 9372PX, 9372PX-E, 9396PX, and 9500 platform switches do not support FEXes (Fabric extenders).

Note: Please note the following:

■        The 9408 and line card is not supported with the 2300 FEX.

■        Cisco Nexus 9300 Series switches do not support FEX on uplink modules (ALE).

■        For FEX HIF port channels, we recommend that you enable STP port type edge using the spanning tree port type edge [trunk] command.

■        The Cisco 2248PQ, 2348TQ, and 2348UPQ FEXes support connections to the Nexus 9300 or 9500 switches by using supported breakout cables to connect a QSFP+ uplink on the FEX and an SFP+ link on the parent switch (4x10G links).

Note: For Cisco Nexus 9500 switches, 4x10G breakout for FEX connectivity is not supported.

New and Changed Information

This section lists the following topics:

■        New Hardware Features in Cisco NX-OS Release 7.0(3)I4(2)

■        New Software Features in Cisco NX-OS Release 7.0(3)I4(2)

New Hardware Features in Cisco NX-OS Release 7.0(3)I4(2)

Cisco NX-OS Release 7.0(3)I4(2) supports the following new hardware:

■        Cisco Nexus 93108TC-EX switch (N9K-C93108TC-EX) – 1 rack unit (RU) switch with 48 10GBASE-T ports and six fixed 100-Gigabit QSFP28 (optical) ports. The 10GBASE-T ports support 100-Megabit, 1-Gigabit, and 10-Gigabit speeds, and the QSFP28 ports support 40- and 100-Gigabit speeds.

■        Cisco Nexus 93180YC-EX switch (N9K-C93180YC-EX) – 1 rack unit (RU) switch with 48 downlink SFP+ ports that you can configure to work as 1-, 10-, or 25-Gigabit ports, and it has six fixed uplink QSFP28 ports that you can configure to work as 40- or 100-Gigabit ports (or a combination of 10-, 25-, 40-, 50-, and 100-Gigabit connectivity).

■        Cisco Nexus 9504 (N9K-C9504-FM-E) 100-Gigabit fabric module supporting 100-Gigabit –EX line cards

■        Cisco Nexus 9508 (N9K-C9508-FM-E) 100-Gigabit fabric module supporting 100-Gigabit –EX line cards

■        Cisco Nexus N9K-X9732C-EX I/O module – 32-port 40-/100-Gigabit Ethernet QSFP28 line card (supported by the 100-Gigabit –E fabric modules (N9K-C9504-FM-E and N9K-C9508-FM-E)

New Software Features in Cisco NX-OS Release 7.0(3)I4(2)

Cisco NX-OS Release 7.0(3)I4(2) supports the following new software features:

FEX Features

FEX Layer 3 – Added Layer 3 support for FEX interfaces and subinterfaces on Cisco Nexus 9300 Series switches.

For more information, see the Cisco Nexus 2000 Series NX-OS Fabric Extender Configuration Guide for Cisco Nexus 9000 Series Switches.

Interfaces Features

Cisco SFP+ adapter module – Added 25-Gigabit optics support to the 8-port CVR-2QSFP28-8SFP adapter for the Cisco Nexus 3232C and 9236C switches.

For more information, see the Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide and the Cisco Nexus 3232C and 3264Q Switches Read Me First.

IP Fabric for Media Solution Features

Cisco’s IP fabric for media solution replaces the SDI router in live production studios with an IP-based infrastructure. The Cisco Nexus 9000 Series switches in conjunction with the Cisco non-blocking multicast (NBM) algorithm (an intelligent traffic management algorithm) provides a reliable, scalable IP fabric for the broadcast industry. In addition, this IP fabric solution provides zero-drop multicast transport and support for PTP media profiles. For more information, see the IP fabric for media release notes, solution guide, and video.

Multicast Routing Features

IGMP snooping – Added the ip igmp snooping report-flood and ip igmp snooping proxy-leave use-group-address commands.

For more information, see the Cisco Nexus 9000 Series NX-OS Multicast Routing Configuration Guide.

QoS Features

■        LLDP DCBX TLV enhancement – Changed the behavior of the no lldp tlv-select dcbxp command such that priority flow control (PFC) mode will be disabled for interfaces on both sides of back-to-back switches.

■        Non-ECN-capable behavior enhancement – Added the congestion-control random-detect forward-nonecn command to allow non-ECN-capable traffic to bypass WRED thresholds. This feature is supported only for Cisco Nexus 9200 Series switches, Cisco Nexus 93108TC-EX and 93180YC-EX switches, and Cisco Nexus 9508 switches with the X9732C-EX line card.

■        PFC enhancements – Added commands to globally disable PFC on all interfaces and to configure a watchdog interval to detect whether packets in a no-drop queue are being drained within a specified time period. These enhancements are supported only for Cisco Nexus 9200 Series switches, Cisco Nexus 93108TC-EX and 93180YC-EX switches, and Cisco Nexus 9508 switches with the X9732C-EX line card.

For more information, see the Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide.

System Management Features

Added the CISCO-ERR-DISABLE and Q-BRIDGE-MIB MIBs and enhancements to the CISCO-SWITCH-QOS-MIB MIB.

For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide.

Caveats

This section includes the following topics:

■        Resolved Caveats—Cisco NX-OS Release 7.0(3)I4(2)

■        Open Caveats—Cisco NX-OS Release 7.0(3)I4(2)

■        Known Behaviors—Cisco NX-OS Release 7.0(3)I4(2)

Resolved Caveats—Cisco NX-OS Release 7.0(3)I4(2)

Table 14 lists the Resolved Caveats in Cisco NX-OS Release 7.0(3)I4(2). Click the bug ID to access the Bug Search tool and see additional information about the bug.

Table 14 Resolved Caveats in Cisco NX-OS Release 7.0(3)I4(2)

Open Caveats—Cisco NX-OS Release 7.0(3)I4(2)

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

Table 15 Open Caveats in Cisco NX-OS Release 7.0(3)I4(2)

Known Behaviors—Cisco NX-OS Release 7.0(3)I4(2)

Table 16 lists the known behaviors in the Cisco NX-OS Release 7.0(3)I4(2). Click the bug ID to access the Bug Search tool and see additional information about the bug.

Table 16 Known Behaviors in Cisco NX-OS Release 7.0(3)I4(2)

 

Upgrade and Downgrade

To perform a software upgrade or downgrade, follow the instructions in the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x.

For information about an In Service Software Upgrade (ISSU), see the Cisco NX-OS ISSU Support application.

Note: Upgrading from Cisco NX-OS 7.0(3)I1(2), 7.0(3)I1(3), or 7.0(3)I1(3a) requires installing a patch for Cisco Nexus 9500 platform switches only. For more information on the upgrade patch, see Upgrade Patch Instructions.

Limitations

This section lists limitations related to Cisco NX-OS Release 7.0(3)I4(2).

■        Ingress queuing policy is supported only at the system level (and not at the interface level) for Cisco Nexus 9508 switches with the X9732C-EX line card and Cisco Nexus 93108TC-EX and 93180YC-EX switches.

■        QinVNI  has the following limitations:

¯    Single tag is supported on Cisco Nexus 9300 Series switches. It can be enabled by unconfiguring the overlay-encapsulation vxlan-with-tag command from interface nve:

N9564PX-2(config)# int nve 1

N9564PX-2(config-if-nve)# no overlay-encapsulation vxlan-with-tag

N9564PX-2# sh run int nve 1

                               

!Command: show running-config interface nve1

!Time: Wed Jul 20 23:26:25 2016

 

version 7.0(3u)I4(2u)

 

interface nve1

  no shutdown

  source-interface loopback0

  host-reachability protocol bgp

  member vni 900001 associate-vrf

  member vni 2000980

    suppress-arp

    mcast-group 225.4.0.1

 

¯    Single tag is not supported on Cisco Nexus 9500 platform switches; only double tag is supported.

¯    When upgrading from Cisco Nexus 7.0(3)I3(1)  or Release 7.0(3)I4(1) to Release 7.0(3)I4(2) with Cisco Nexus 9300 Series switches without the overlay-encapsulation vxlan-with-tag command under interface nve, you should add overlay-encapsulation vxlan-with-tag under the nve interface in the older release before starting the ISSU upgrade. We were only supporting double tag in Cisco Nexus 7.0(3)I3(1)  and  Release 7.0(3)I4(1) . We now support single tag also in Release 7.0(3)I4(2).

■        Resilient hashing (port-channel load-balancing resiliency) and VXLAN configurations are not compatible with VTEPs using ALE uplink ports. Please note that resilient hashing is disabled by default.

■        Fast reload is not supported for any Cisco Nexus 3000 or 9000 Series switches starting with Cisco NX-OS Release 7.0(3)I4(1).

■        CoPP (Control Plane Policing) cannot be disabled. If you attempt to disable it in Cisco NX-OS Release 7.0(3)I4(2), an error message appears. In previous releases, attempting to disable CoPP causes packets to be rate limited at 50 packets per seconds.

■        Skip CoPP policy option has been removed from the Cisco NX-OS initial setup utility because using it can impact the control plane of the network.

■        hardware profile front portmode command is not supported on the Cisco Nexus 9000 Series switches.

■        PV (Port VLAN) configuration through an interface range is not supported.

■        Layer 3 routed traffic for missing Layer 2 adjacency information is not flooded back onto VLAN members of ingress units when the source MAC address of routed traffic is a non-VDC (Virtual Device Context) MAC address. This limitation is for hardware flood traffic and can occur when the SVI (Switched Virtual Interface) has a user-configured MAC address.

■        neighbor-down fib-accelerate command is supported in a BGP-only environment.

■        Uplink modules should not be removed from a Cisco Nexus 9300 Series switch that is running Cisco NX-OS Release 7.0(3)I4(2). The ports on uplink modules should be used only for uplinks.

■        PortLoopback and BootupPortLoopback tests are not supported.

■        PFC (Priority Flow Control) and LLFC (Link-Level Flow Control) are supported for all Cisco Nexus 9300 and 9500 platform hardware except for the 100G 9408PC line card and the 100G M4PC generic expansion module (GEM).

■        FEXes configured with 100/full-duplex speed, without explicitly configuring the neighboring device with 100/full-duplex speed, will not pass data packet traffic properly. This occurs with or without the link appearing to be “up.”

¯    no speed–Auto negotiates and advertises all speeds (only full duplex).

¯    speed 100–Does not auto negotiate; pause cannot be advertised. The peer must be set to not auto negotiate (only 100 Mbps full duplex is supported).

¯    speed 1000–Auto negotiates and advertises pause (advertises only for 1000 Mbps full duplex).

■        Eight QoS groups are supported only on modular platforms with the Cisco Nexus 9300 N9K-M4PC-CFP2  uplink module, and the following Cisco Nexus 9500 platform line cards:

¯    N9K-X9432PQ

¯    N9K-X9464PX

¯    N9K-X9464TX

¯    N9K-X9636PQ

■        Flooding for Microsoft Network Load Balancing (NLB) unicast mode is supported only on Cisco Nexus 9500 platform switches. However, if the NLB servers are connected on FEX HIFs, the flooding does not work. NLB is not supported in max-host system routing mode, and NLB multicast mode is not supported.

Note: To work around the situation of Unicast NLB limitation, Cisco can statically hard code the address resolution protocol (ARP) and MAC address pointing to the correct interface. Please refer to bug ID CSCuq03168 in detail in the Open Caveats section.

■        TCAM resources are not shared when:

¯    Applying VACL (VLAN ACL) to multiple VLANs

¯    Routed ACL (Access Control List) is applied to multiple SVIs in the egress direction

■        Cisco Nexus 9000 Series switch hardware does not support range checks (layer 4 operators) in egress TCAM. Because of this, ACL/QoS policies with layer 4 operations-based classification need to be expanded to multiple entries in the egress TCAM. Egress TCAM space planning should take this limitation into account.

■        Applying the same QoS policy and ACL on multiple interfaces requires applying the qos-policy with the no-stats option to share the label.

■        Multiple port VLAN mappings configured on an interface during a rollback operation causes the rollback feature to fail.

■        The following switches support QSFP+ with the QSA (QSFP to SFP/SFP+ Adapter) (40G to 10G QSA):

¯    N9K-C93120TX

¯    N9K-C93128TX

¯    N9K-C9332PQ

¯    N9K-C9372PX

¯    N9K-C9372PX-E

¯    N9K-C9372TX

¯    N9K-C9396PX

       Note: The Cisco Nexus 9300 support for the QSFP+ breakout has the following limitations:

■        Only 10G can be supported using QSA on 40G uplink ports on Cisco Nexus 9300 switches in NX-OS. 

■        1G with QSA is not supported.

■        For the Cisco Nexus 9332PQ switch, all ports except 13-14 and 27-32 can support breakout

■        All ports in the QSA speed group must operate at the same speed (see the configuration guide)

■        The following switches support the breakout cable (40G ports to 4x10G ports):

¯    N9K-C9332PQ

¯    N9K-X9436PQ

¯    N9K-X9536PQ

¯    N9K-C93180YC-EX

¯    N9K-C93108TC-EX

¯    N9K-X9732C-EX line card

■        Weighted ECMP (Equal-Cost Multi-Path) Nexus 3000 feature is not supported on the Cisco Nexus 9000 Series switch.

■        When upgrading from N9K-X94xx, N9K-X95xx, and N9K-X96xx line cards to N9K-X9732C-EX line cards and their fabric modules, upgrade the Cisco NX-OS software before inserting the line cards and fabric modules. Failure to do so can cause a diagnostic failure on the line card and no TCAM space to be allocated. You must use the write_erase command followed by the reload command.

■        Limitations for ALE (Application Link Engine) uplink ports are listed at the following URL:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/ale_ports/b_Limitations_for_ALE_Uplink_Ports_on_Cisco_Nexus_9000_Series_Switches.html

Guidelines and Limitations for Private VLANs

This section provides guidelines and limitations for configuring private VLANs.

■        Configuring Private VLANs

■        Secondary and Primary VLAN Configuration

■        Private VLAN Port Configuration

■        Limitations with Other Features

Configuring Private VLANs

Private VLANs have the following configuration guidelines and limitations:

■        Private VLANs must be enabled before the device can apply the private VLAN functionality.

■        VLAN interface feature must be enabled before the device can apply this functionality.

■        VLAN network interfaces for all VLANs that you plan to configure as secondary VLANs should be shut down before being configured.

■        When a static MAC is created on a regular VLAN, and then that VLAN is converted to a secondary VLAN, the Cisco NX-OS maintains the MAC that was configured on the secondary VLAN as the static MAC.

■        Private VLANs support port modes as follows:

¯    Community host

¯    Isolated host

¯    Isolated host trunk

¯    Promiscuous

¯    Promiscuous trunk

■        When configuring PVLAN promiscuous or PVLAN isolated trunks, it is recommended to allow non-private VLANs in the list specified by the switchport private-vlan trunk allowed id command.

■        Private VLANs are mapped or associated depending on the PVLAN trunk mode.

■        Private VLANs support the following:

¯    Layer 2 forwarding

¯    PACLs (Port Access Control Lists)

¯    Promiscuous trunk

¯    PVLAN across switches through a regular trunk port

¯    RACLs (Router Access Control Lists)

■        Private VLANs support SVIs as follows:

¯    HSRP (Hot Standby Router Protocol) on the primary SVI

¯    Primary and secondary IPs on the SVI

¯    SVI allowed only on primary VLANs

■        Private VLANs support STP as follows:

¯    MST (Multiple Spanning Tree)

¯    RSTP (Rapid Spanning Tree Protocol)

■        Private VLANs port mode is not supported on the following:

¯    40G interfaces of the Cisco Nexus C9396PX or Cisco Nexus C93128TX

¯    Cisco Nexus 3164Q

■        Private VLANs do not provide port mode support for the following:

¯    Port channels

¯    vPC (Virtual Port Channel) interfaces

■        Private VLANs do not provide support on breakout.

■        Private VLANs do not provide support for the following:

¯    DHCP (Dynamic Host Channel Protocol) snooping

¯    IP multicast or IGMP snooping

¯    PVLAN QoS

¯    SPAN (Switch Port Analyzer) when the source is a PVLAN VLAN

¯    Tunnels

¯    VACLs

¯    VTP (VLAN Trunk Protocol)

¯    VXLANs

■        Shared interfaces cannot be configured to be part of a private VLAN. For more details, see the Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide.

■        Configuring multiple isolated VLAN configurations per PVLAN group is allowed by the Cisco NX-OS CLI. However, such a configuration is not supported. A PVLAN group can have at most one isolated VLAN.

Secondary and Primary VLAN Configuration

Follow these guidelines when configuring secondary or primary VLANs in private VLANs:

■        Default VLANs (VLAN1), or any of the internally allocated VLANs, cannot be configured as primary or secondary VLANs.

■        VLAN configuration (config-vlan) mode must be used to configure private VLANs.

■        Primary VLANs can have multiple isolated and community VLANs associated with it. An isolated or community VLAN can be associated with only one primary VLAN.

■        Private VLANs provide host isolation at Layer 2. However, hosts can communicate with each other at Layer 3.

■        PVLAN groups can have one isolated VLAN at most. Multiple isolated VLAN configurations per primary VLAN configurations are not supported.

■        When a secondary VLAN is associated with the primary VLAN, the STP parameters of the primary VLAN, such as bridge priorities, are propagated to the secondary VLAN. However, STP parameters do not necessarily propagate to other devices. You should manually check the STP configuration to ensure that the spanning tree topologies for the primary, isolated, and community VLANs match exactly so that the VLANs can properly share the same forwarding database.

■        For normal trunk ports, note the following:

¯    Separate instances of STP exist for each VLAN in the private VLAN.

¯    STP parameters for the primary and all secondary VLANs must match.

¯    Primary and all associated secondary VLANs should be in the same MST instance.

■        For non-trunking ports, STP is aware only of the primary VLAN for any private VLAN host port; STP runs only on the primary VLAN for all private VLAN ports.

Note: We recommend that you enable BPDU Guard on all ports that you configure as a host port; do not enable this feature on promiscuous ports.

■        Private VLAN promiscuous trunk ports allow you to configure a maximum of 16 private VLAN primary and secondary VLAN pairs on each promiscuous trunk port.

■        For private VLAN isolated trunk ports, note the following:

¯    You can configure a maximum of 16 private VLAN primary and secondary VLAN pairs on each isolated trunk port.

¯    The native VLAN must be either a normal VLAN or a private VLAN secondary VLAN. You cannot configure a private VLAN primary port as the native VLAN for a private VLAN isolated trunk port.

■        Downgrading a system that has private VLAN ports configured requires unconfiguring the ports.

■        Before configuring a VLAN as a secondary VLAN, you must shut down the VLAN network interface for the secondary VLAN.

Private VLAN Port Configuration

Follow these guidelines when configuring private VLAN ports:

■        Deleting a VLAN used in the private VLAN configuration causes private VLAN ports (promiscuous ports or host ports, not trunk ports) that are associated with the VLAN to become inactive.

■        Layer 2 access ports that are assigned to the VLANs that you configure as primary, isolated, or community VLANs are inactive while the VLAN is part of the private VLAN configuration. Layer 2 trunk interfaces, which may carry private VLANs, are active and remain part of the STP database.

■        Use only the private VLAN configuration commands to assign ports to primary, isolated, or community VLANs.

Limitations with Other Features

Consider these configuration limitations with other features when configuring private VLANs:

Note: In some cases, the configuration is accepted with no error messages, but the commands have no effect.

■        After configuring the association between the primary and secondary VLANs and deleting the association, all static MAC addresses that were created on the primary VLANs remain on the primary VLAN only.

■        After configuring the association between the primary and secondary VLANs:

¯    Static MAC addresses for the secondary VLANs cannot be created.

¯    Dynamic MAC addresses that learned the secondary VLANs are aged out.

■        Destination SPAN ports cannot be isolated ports. However, a source SPAN port can be an isolated port.

■        Ensure consistent PVLAN type, states, and configuration across vPC peers. There is currently no PVLAN consistency check for vPC. Inconsistent PVLAN configs across vPV peers may end up in incorrect forwarding and impacts.

■        In private VLANs, STP controls only the primary VLAN.

■        Private VLAN host or promiscuous ports cannot be SPAN destination ports.

■        Private VLAN ports can be configured as SPAN source ports.

■        vPC pairing between T2 and TH platforms is not recommended.

Note: See the Cisco Nexus 9000 Series NX-OS Security Configuration Guide for information on configuring static MAC addresses.

Unsupported Features

This section lists features that are not supported in the current release.

■        VXLAN

■        DHCP

■        FEX

■        Cisco Nexus 3232C and 3264Q Switches

■        Cisco 9200 Nexus Series, 93108TC-EX, and 93180YC-EX Switches

■        Cisco Nexus 9408 Line Card and 9300 Series Switches

■        Cisco Nexus 9732C-EX Line Card

■        Other Unsupported Features

VXLAN

This section lists VXLAN features that are not supported.

■        ACL and QoS for VXLAN traffic in the network-to-access direction are not supported.

■        Consistency checkers are not supported for VXLAN tables.

■        DHCP snooping and DAI features are not supported on VXLAN VLANs.

■        IGMP snooping is not supported on VXLAN VLANs.

■        Native VLANs for VXLAN are not supported. All traffic on VXLAN Layer 2 trunks needs to be tagged.

■        QoS buffer-boost is not applicable for VXLAN traffic.

■        QoS classification is not supported for VXLAN traffic in the network-to-access direction.

■        Static MAC pointing to remote VTEP (VXLAN Tunnel End Point) is not supported with BGP EVPN (Ethernet VPN).

■        TX SPAN (Switched Port Analyzer)  for VXLAN traffic is not supported for the access-to-network direction.

■        VXLAN routing and VXLAN Bud Nodes features on the 3164Q platform are not supported.

VXLAN ACL Limitations

The following ACL related features are not supported:

■        Ingress RACL that is applied on an uplink Layer 3 interface that matches on the inner or outer payload in the network-to-access direction (decapsulated path).

■        Egress RACL that is applied on an uplink Layer 3 interface that matches on the inner or outer payload in the access-to-network direction (encapsulated path).

■        Egress VACL for decapsulated VXLAN traffic.

Note: We recommend that you use a PACL or VACL on the access side to filter out traffic entering the overlay network.

DHCP

DHCP subnet broadcast is not supported.

FEX

■        VTEP connected to FEX host interface ports is not supported.

■        ASCII replay with FEX needs be done twice for HIF configurations to be applied. The second time should be done after the FEXs have come up.

■        Cisco Nexus 9300 Series switches do not support FEX on uplink modules (ALE).

■        FEX is supported only on the Cisco Nexus 9332PQ, 9372PX, 9372PX-E, 9396PX, and 9500 platform switches (FEX is not supported on the N9K-X9732C-EX line card, 93180YC-EX and 93108TC-EX switches, and Cisco Nexus 9200 platforms).

■        FEX vPC is not supported between any model of FEX and the Nexus 9300 (TOR) and 9500 Switches (EOR) as the parent switches.

■        IPSG (IP Source Guard) is not supported on FEX ports.

Cisco Nexus 3232C and 3264Q Switches

The following features are not supported for the Cisco Nexus 3232C and 3264Q switches:

■        3264Q and 3232C platforms do not support the PXE boot of the NXOS image from the loader.

■        Automatic negotiation support for 25G and 50G ports on the Cisco Nexus 3232C switch

■        Cisco Nexus 2000 Series Fabric Extenders (FEX)

■        Cisco NX-OS to ACI conversion (The Cisco Nexus 3232C and 3264Q switches operate only in Cisco NX-OS mode.)

■        DCBXP

■        Designated router delay

■        DHCP subnet broadcast is not supported

■        Due to a Poodle vulnerability, SSLv3 is no longer supported

■        FCoE NPV

■        Intelligent Traffic Director (ITD)

■        ISSU

■        Policy-based routing (PBR)

■        Port loopback tests

■        Resilient hashing

■        SPAN on CPU as destination

■        Virtual port channel (vPC) peering between Cisco Nexus 3232C or 3264Q switches and Cisco Nexus 9300 Series switches or between Cisco Nexus 3232C or 3264Q switches and Cisco Nexus 3100 Series switches

■        VXLAN

Cisco 9200 Nexus Series, 93108TC-EX, and 93180YC-EX Switches

The following features are not supported for the Cisco Nexus 9200 Series switches and the Cisco Nexus 93108TC-EX and 93180YC-EX switches:

■        Segment routing, static MPLS, and MPLS stripping (supported for Cisco Nexus 9200 Series switches but not for Cisco Nexus 93108TC-EX and 93180YC-EX switches)

■        64-bit ALPM routing mode

■        9272PQ and 92160YC platforms do not support the PXE boot of the NXOS image from the loader.

■        ACL filters to span subinterface traffic on the parent interface

■        Cisco Nexus 2000 Series Fabric Extenders

■        DCBXP for LLDP

■        Egress port ACLs

■        Egress QoS policer or marking

■        FCoE NPV

■        FEX

■        GRE v4 payload over v6 tunnels

■        Intelligent Traffic Director

■        IP length-based matches

■        IPinIP on 92160

■        ISSU

■        Layer 2 Q-in-Q, due to a hardware limitation (supported for Cisco Nexus 93108TC-EX and 93180YC-EX switches but not for Cisco Nexus 9200 Series switches)

■        Micro-burst detection

■        MTU (Multi Transmission  Unit) checks for packets received with an MPLS header

■        OpenFlow, due to a hardware limitation

■        Packet-based statistics for traffic storm control (only byte-based statistics are supported)

■        Policy-based routing

■        PV routing for VXLAN

■        PVLANs

■        Q-in-VNI and Q-in-Q for VXLAN

■        Resilient hashing for ECMP

■        Resilient hashing for port-channel

■        Rx SPAN for multicast if the SPAN source and destination are on the same slice and no forwarding interface is on the slice

■        sFlow

■        Traffic storm control for copy-to-CPU packets

■        Traffic storm control with unknown multicast traffic

■        Tx SPAN for multicast, unknown multicast, and broadcast traffic

■        VACL redirects for TAP aggregation

Cisco Nexus 9408 Line Card and 9300 Series Switches

The following features are not supported for the Cisco Nexus N9K-X9408PC-CFP2 line card and Cisco Nexus 9300 Series switches with generic expansion modules (N9K-M4PC-CFP2):

■        Breakout ports

■        Port-channel (No LACP)

■        vPC

■        MCT (Multichassis EtherChannel Trunk)

■        FEX

■        PTP (Precision Time Protocol)

■        PFC/LLFC

■        802.3x

■        PVLAN

■        Storm Control

■        VXLAN access port.

■        SPAN destination/ERSPAN destination IP

■        Shaping support on 100g port is limited

■        Only support 40G flows

Cisco Nexus 9732C-EX Line Card

The following features are not supported for Cisco Nexus 9508 switches with an N9K-X9732C-EX line card:

■        FEX

■        TAP aggregation

■        SPAN port-channel destinations

■        Marker packet support for ERSPAN Type 3

 Other Unsupported Features

The following lists other features not supported in the current release:

■        Cisco Nexus 9300 Series switches do not support the 64-bit ALPM routing mode.

■        Due to a Poodle vulnerability, SSLv3 is no longer supported.

■        IPSG is not supported on the following:

¯    The last six 40G physical ports on the 9372PX, 9372TX, and 9332PQ switches

¯    All 40G physical ports on the 9396PX, 9396TX, and 93128TX switches

Related Documentation

The entire Cisco Nexus 9000 Series NX-OS documentation set is available at the following URL:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/tsd-products-support-series-home.html

The Cisco Nexus 3164Q Switch - Read Me First is available at the following URL:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3164/sw/6x/readme/b_Cisco_Nexus_3164Q_Switch_Read_Me_First.html

The Cisco Nexus 31128PQ Switch - Read Me First is available at the following URL:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus31128/sw/readme/b_Cisco_Nexus_31128PQ_Switch_Read_Me_First.html

The Cisco Nexus 3232C/3264Q Switch - Read Me First is available at the following URL:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3232and3264/sw/7x/readme/b_Cisco_Nexus_3232C_and_3264Q_Switch_Read_Me_First.html

New Documentation

The new Hardware Installation Guides are available:

■        Cisco Nexus 93108TC-EX NX-OS-Mode Switch Hardware Installation Guide

■        Cisco Nexus 93180YC-EX NX-OS-Mode Switch Hardware Installation Guide

■        Cisco Nexus 9000 Series NX-OS IP Fabric for Media Release Notes, Release 7.0(3)I4(2)

■        Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide

■        Cisco IP Fabric for Media Solution video

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Open a service request online at:

https://tools.cisco.com/ServiceRequestTool/create/launch.do

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

 

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)

Cisco Nexus 9000 Series NX-OS Release Notes, Release 7.0(3)I4(2)

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