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

This document describes the features, caveats, and limitations for Cisco NX-OS Release 7.0(3)I6(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

Date

Description

September 28, 2020

Upgrade and Downgrade section revised.

January 24, 2020

Added CSCvc95008 to Known Behaviors.

September 19, 2018

Updated the Upgrade Instructions regarding upgrades from Release 7.0(3)I2(2b).

July 25, 2018

Added CSCuy08187 to Open Caveats.

January 31, 2018

Updated Limitations for IPv6 Multicast.

December 20, 2017

Updated the Upgrade Instructions and Downgrade Instructions.

October 23, 2017

Updated the ISSU list in the Upgrade Instructions.

October 20, 2017

Added CSCvg14780 to the Open Caveats table.

October 19, 2017

Removed limitation related to Cisco Nexus 9272Q, 9236C, and 92160YC-X switches.

Added CSCvg01785 to the Open Caveats table.

October 18, 2017

Created the release notes for Release 7.0(3)I6(2).

Contents

Introduction

System Requirements

New and Changed Information

Caveats

Upgrade and Downgrade

Limitations

Guidelines and Limitations for Private VLANs

Guidelines and Limitations for Fabric Extenders

Unsupported Features

Related Documentation

Obtaining Documentation and Submitting a Service Request

■

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 Device Hardware

■      Supported Optics

■      Supported FEX Modules

Supported Device Hardware

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

■      Table 2 lists the Cisco Nexus 9000 Series fabric modules

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

■      Table 4 lists the Cisco Nexus 9000 Series line cards

■      Table 5 lists the Cisco Nexus 9000 Series power supplies

■      Table 6 lists the Cisco Nexus 9000 Series supervisor modules

■      Table 7 lists the Cisco Nexus 9000 Series system controllers

■      Table 8 lists the Cisco Nexus 9000 Series uplink modules

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

■      Table 11 lists the Cisco Nexus 3164Q switch hardware

■      Table 12 lists the Cisco Nexus 31128PQ switch hardware

Table 2 Cisco Nexus 9000 Series Fabric Modules

Product ID

Hardware

Quantity

N9K-C9504-FM

Cisco Nexus 9504 40-Gigabit fabric module

3 to 6 depending on line cards

N9K-C9504-FM-E

100-Gigabit -E fabric module (for the Cisco Nexus 9504 chassis) that supports the 100-Gigabit (-EX) line cards. When used, there must be 4 of these fabric modules installed in fabric slots 22, 23, 24, and 26.

4

N9K-C9504-FM-S

100-Gigabit -S fabric module (for the Cisco Nexus 9504 chassis) that supports the 100-Gigabit (-S) line cards. When used, there must be 4 of these fabric modules installed in fabric slots 22, 23, 24, and 26.

4

N9K-C9508-FM

Cisco Nexus 9508 Series 40-Gigabit fabric module

3-6 depending on the line cards

N9K-C9508-FM-E

100-Gigabit -E fabric module (for the Cisco Nexus 9508 chassis) that supports the 100-Gigabit (-EX) line cards. When used, there must be 4 of these fabric modules installed in fabric slots 22, 23, 24, and 26.

4

N9K-C9508-FM-S

100-Gigabit -S fabric module (for the Cisco Nexus 9508 chassis) that supports the 100-Gigabit (-S) line cards. When used, there must be 4 of these fabric modules installed in fabric slots 22, 23, 24, and 26.

4

N9K-C9508-FM-Z

Fabric blank with Fan Tray Power Connector module used in place of a fabric module that has been removed from fabric slots 22, 24, or 26 during lab verification test.

1

N9K-C9516-FM

Cisco Nexus 9500 Series 40-Gigabit fabric module

3-6 depending on the line cards

N9K-C9516-FM-E

100-Gb –E fabric module (for the Cisco Nexus 9516 chassis_ that supports the 100-Gb (-EX) line cards. When used, there must be four of these fabric modules installed in fabric slots 22, 23, 24, and 26.

4

N9K-C9516-FM-Z

Fabric blank with Fan Tray Power Connector module used in place of a fabric module that has been removed from fabric slots 22, 24, or 26 during lab verification test.

1

Table 3 Cisco Nexus 9000 Series Fans and Fan Trays

Product ID

Hardware

Quantity

N9K-C9300-FAN1

Cisco Nexus 9300 fan 1 module with port-side intake airflow (burgundy coloring)

Note: Supports early versions of the Cisco Nexus 9396 switch (N9K-C9396PX).

3

N9K-C9300-FAN1-B

Cisco Nexus 9300 fan 1 module with port-side exhaust airflow (blue coloring)

Note: Supports early versions of the Cisco Nexus 9396 switch (N9K-C9396PX).

3

N9K-C9300-FAN2

Cisco Nexus 9300 fan 2 module with port-side intake airflow (burgundy coloring)

Note: Supports the Cisco Nexus 93128TX, 9396PX, and 9396TX switches.

3

N9K-C9300-FAN2-B

Cisco Nexus 9300 fan 2 module with port-side exhaust airflow (blue coloring)

Note: Supports the Cisco Nexus 93128TX, 9396PX, and 9396TX switches.

3

N9K-C9300-FAN3

Cisco Nexus 9300 fan 2 module with port-side intake airflow (burgundy coloring)

Note: Supports the Cisco Nexus 93120TX, 92304QC, and 9272Q switches.

2

N9K-C9300-FAN3-B

Cisco Nexus 9300 fan 2 module with port-side exhaust airflow (blue coloring)

Note: Supports the Cisco Nexus 93120TX, 92304QC, and 9272Q switches.

2

N9K-C9504-FAN

Cisco Nexus 9504 fan tray

3

N9K-C9508-FAN

Cisco Nexus 9508 fan tray

3

NXA-FAN-30CFM-B

Cisco Nexus 9200 and 9300 fan module with port-side intake airflow (burgundy coloring)

Note: Supports the Cisco Nexus 93180LC-EX, 92160YC-X, 9236C, 93108TC-EX, 93180YC-EX, 9332PQ, 9372PX, 9372PX-E, 9372TX, and 9372TX-E switches.

4

NXA-FAN-30CFM-F

Cisco Nexus 9200 and 9300 fan module with port-side exhaust airflow (blue coloring)

Note: Supports the Cisco Nexus 93180LC-EX, 92160YC-X, 9236C, 93108TC-EX, 93180YC-EX, 9332PQ, 9372PX, 9372PX-E, 9372TX, and 9372TX-E switches.

4

NXA-FAN-35CFM-PE

Cisco Nexus 9200 fan module with port-side exhaust airflow (blue coloring)

Note: Supports the Cisco Nexus 92300YC switch.

4

NXA-FAN-35CFM-PI

Cisco Nexus 9200 fan module with port-side intake airflow (burgundy coloring)

Note: Supports the Cisco Nexus 92300YC switch.

4

Table 4 Cisco Nexus 9500 Series Line Cards

Product ID

Description

Quantity

N9K-X9408PC-CFP2

Line card with 8 100-Gigabit CFP2 ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9432C-S

Line card with 32 100-Gigabit QSFP28 ports (supported by four 100-Gigabit –S fabric modules [N9K-C9504-FM-S and N9K-C9508-FM-S])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

N9K-X9432PQ

Line card with 32 40-Gigabit QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

Note: This line card supports static breakout.

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9464PX

Line card with 48 10-Gigabit SFP+ ports and 4 40-Gigabit QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9464TX

Line card with 48 10GBASE-T ports and 4 40-Gigabit QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K- X9464TX2

Line card with 48 10GBASE-T ports and 4 40-Gigabit QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9536PQ

Line card with 36 40-Gigabit Ethernet QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9564PX

Line card with 48 1-/10-Gigabit SFP+ ports and 4 40-Gigabit QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9564TX

Line card with 48 1-/10-GBASE-T ports and 4 40-Gigabit QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM, N9K-C9508-FM, and N9K-9516FM])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9636PQ

Line card with 36 40-Gigabit QSFP+ ports (supported by 40-Gigabit fabric modules [N9K-C9504-FM and N9K-C9508-FM])

Note: Not supported on the Cisco Nexus 9516 switch (N9K-C9516).

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

N9K-X9732C-EX

Line card with 32 40-/100-Gigabit Ethernet QSFP28 ports (supported by 100-Gigabit –E fabric modules [N9K-C9504-FM-E, N9K-C9508-FM-E, and N9K-C9516-FM-E])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X9736C-EX

Line card with 36 40-/100 Gigabit Ethernet QSFP28 ports (supported by 100-Gigabit –E fabric modules [N9KC9504-FM-E, N9K-C9508-FM-E, and N9K-9516-FM-E[).

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

N9K-X97160YC-EX

Line card with 48 10-/25-Gigabit Ethernet SFP28 ports and 4 40-/100-Gigabit Ethernet QSFP28 ports (supported by 100-Gigabit –E fabric modules [N9K-C9504-FM-E, N9K-C9508-FM-E, and N9K-9516-FM-E])

■      1-4 (Cisco Nexus 9504)

■      1-8 (Cisco Nexus 9508)

■      1-16 (Cisco Nexus 9516)

Table 5 Cisco Nexus 9000 Series Power Supplies

Product ID

Hardware

Quantity

N9K-PAC-500W-PE

500-W AC power supply, port-side exhaust airflow (blue coloring)

2

N9K-PAC-500W-PI

500-W AC power supply, port-side intake airflow (burgundy coloring)

2

N9K-PAC-650W

650-W AC power supply, port-side intake airflow (burgundy coloring)

2

N9K-PAC-650W-B

650-W AC power supply, port-side exhaust airflow (blue coloring)

2

N9K-PAC-1200W

1200-W AC power supply, port-side intake airflow (burgundy coloring)

2

N9K-PAC-1200W-B

1200-W AC power supply, port-side exhaust airflow (blue coloring)

2

N9K-PAC-3000W-B

3000-W AC power supply

■      Up to 4 (Cisco Nexus 9504)

■      Up to 8 (Cisco Nexus 9508)

Up to 10 (Cisco Nexus 9516)

N9K-PDC-3000W-B

3000-W DC power supply

■      Up to 4 (Cisco Nexus 9504)

■      Up to 8 (Cisco Nexus 9508)

Up to 10 (Cisco Nexus 9516)

N9K-PUV-1200W

1200-W AC power supply (airflow direction determined by the installed fan modules)

2

N9K-PUV-3000W-B

3000-W Universal AC/DC power supply

■      Up to 4 (Cisco Nexus 9504)

■      Up to 8 (Cisco Nexus 9508)

Up to 10 (Cisco Nexus 9516)

NXA-PAC-500W-PE

Cisco Nexus 9300 500-W AC power supply, port-side exhaust airflow (blue coloring)

2

NXA-PAC-500W-PI

Cisco Nexus 9300 500-W AC power supply, port-side intake airflow (burgundy coloring)

2

NXA-PAC-650W

Cisco Nexus 9200 and 9300 650-W AC power supply (NEBS compliant), port-side intake airflow (burgundy coloring)

2

NXA-PAC-650W-B

Cisco Nexus 9200 and 9300 650 W AC power supply (NEBS compliant), port-side exhaust airflow (blue coloring)

2

NXA-PAC-650W-PE

Cisco Nexus 9200 650-W AC power supply, port-side exhaust airflow (white coloring)

2

NXA-PAC-650W-PI

Cisco Nexus 9200 650-W AC power supply, port-side intake airflow (burgundy coloring)

2

NXA-PAC-1200W

1200-W AC power supply, port-side intake airflow (burgundy coloring)

2

NXA-PAC-1200W-B

1200-W AC power supply, port-side exhaust airflow (blue coloring)

2

NXA-PDC-930W-PE

Cisco Nexus 9300 930-W DC power supply, port-side exhaust airflow (blue coloring)

2

NXA-PDC-930W-PI

Cisco Nexus 9300 930-W DC power supply, port-side intake airflow (burgundy coloring)

2

UCS-PSU-6332-DC

930-W DC power supply with port-side exhaust airflow (gray coloring)

2

UCSC-PSU-930WDC

930-W DC power supply with port-side intake airflow (green coloring)

2

Table 6 Cisco Nexus 9500 Series Supervisor Modules

Product ID

Hardware

Quantity

N9K-SUP-A

Cisco Nexus 9500 Series supervisor A module with 4 cores

2

N9K-SUP-B

Cisco Nexus 9500 Series supervisor B module with 6 cores

2

Table 7 Cisco Nexus 9000 Series Switches

Product ID

Description

N9K-C9236C

Cisco Nexus 9236C 1-RU switch with 36 40-/100-Gigabit QSFP28 ports (144 10-/25-Gigabit ports when using breakout cables).

Note:

·       Beginning with Cisco NX-OS Release 7.0(3)I4(3), 25G CVR-2QSFP28-8SFP adapters are supported on the Cisco Nexus 9236C switches.

Beginning with Cisco NX-OS Release 7.0(3)I5(1), the switch supports 4x10G breakout cables.

N9K-C9272Q

Cisco Nexus 9272Q 2-RU switch with 72 40-Gigabit Ethernet QSFP+ ports (up to 35 of the ports [ports 37-71] also support breakout cables providing up to 140 10-Gigabit connections)

N9K-C9332PQ

Cisco Nexus 9332PQ 1-RU switch with 32 40-Gigabit Ethernet QSFP+ ports and supports 4x10G breakout mode for ports 1 to 26 (except ports 13 and 14). Ports 27 to 32 (ALE uplink ports) support using the QSFP-to-SFP+ Adapter for 10-Gigabit SFP/SFP+ transceivers in QSFP+ ports.

N9K-C9372PX

Cisco Nexus 9372PX 1-RU switch with 48 1-/10-Gigabit Ethernet SFP+ ports and 6 40-Gigabit Ethernet QSFP+ ports.

N9K-C9372PX-E

An enhanced version of the N9K-C9372PX switch.

N9K-C9372TX

Cisco Nexus 9372TX 1-RU switch with 48 1/10GBASE-T ports and 6 40-Gigabit Ethernet QSFP+ ports.

N9K-C9372TX-E

An enhanced version of the N9K-C9372TX switch.

N9K-C9396PX

Cisco Nexus 9396PX 1-RU switch with 48 1-/10-Gigabit Ethernet SFP+ ports and an uplink module with up to 12 40-Gigabit Ethernet QSPF+ ports

N9K-C9396TX

Cisco Nexus 9396TX 1-RU switch with 48 1/10GBASE-T and an uplink module with up to12 40-Gigabit Ethernet QSFP+ ports

N9K-C9504

Cisco Nexus 9504 4-slot modular switch

N9K-C9508

Cisco Nexus 9508 8-slot modular switch

N9K-C9516

Cisco Nexus 9516 16-slot modular switch

N9K-C92160YC-X

Cisco Nexus 92160YC-X 1-RU switch with 48 10-/25-Gigabit SFP+ ports and 6 40-Gigabit QSFP+ ports (4 of these ports support 100-Gigabit QSFP28 optics).

N9K-C92300YC

Cisco Nexus 92300YC 1.5-RU switch with 48 downlink SFP28 ports that you can configure to work as 1-or 10- or 25-Gigabit ports, 18 fixed uplink QSFP28 ports that you can configure to work as 40- or 100-Gigabit ports.

N9K-C92304QC

Cisco Nexus 92304QC 2-RU switch with 56 40-Gigabit Ethernet ports (64 10-Gigabit ports if using breakout cables) and 8 100-Gigabit ports.

N9K-C93108TC-EX

Cisco Nexus 93108TC-EX 1-RU switch with 48 10GBASE-T ports and 6 40/100-Gigabit QSFP28 ports.

N9K-C93120TX

Cisco Nexus 93120TX 2RU switch with 96 1/10GBASE-T ports and 6 40-Gigabit QSFP+ uplink ports.

N9K-C93128TX

Cisco Nexus 93128TX 3-RU switch with 96 1/10GBASE-T ports and an uplink module that supports up to 8 40-Gigabit Ethernet QSPF+ ports (the 1/10GBASE-T ports also support a speed of 100 Megabits per second.)

N9K-C93180LC-EX

Cisco Nexus 93180LC-EX 1-RU switch with 24 downlink QSFP+ ports that you can configure to work as 40- or 50-Gigabit ports, six fixed uplink QSFP28 ports that you can configure to work as 40- or 100-Gigabit ports.

N9K-C93180YC-EX

Cisco Nexus 93180YC-EX 1-RU switch with 48 10-/25-Gigabit Ethernet ports and 6 40/100-Gigabit QSFP28 ports.

Table 8 Cisco Nexus 9000 Series Uplink Modules

Product ID

Hardware

N9K-M4PC-CFP2

Cisco Nexus 9300 uplink module with 4 100-Gigabit Ethernet CFP2 ports. For the Cisco Nexus 93128TX switch, only two of the ports are active. For the Cisco Nexus 9396PX and 9396TX switches, all four ports are active.

N9K-M6PQ

Cisco Nexus 9300 uplink module with 6 40-Gigabit Ethernet QSFP+ ports for the Cisco Nexus 9396PX, 9396TX, and 93128TX switches.

N9K-M6PQ-E

An enhanced version of the Cisco Nexus N9K-M6PQ uplink module.

N9K-M12PQ

Cisco Nexus 9300 uplink module with 12 40-Gigabit Ethernet QSPF+ ports.

Table 9 Cisco Nexus 9500 Series System Controller

Product ID

Hardware

Quantity

N9K-SC-A

Cisco Nexus 9500 Platform System Controller Module

2

Table 10 Cisco Nexus 3232C and 3264Q Switch Hardware

Product ID

Hardware

Quantity

N3K-C3232C

Cisco Nexus 3232C, 32 x 40-Gb/100-Gb 2 x 10-Gb SFP+, 1-RU switch

1

N3K-C3264Q

Cisco Nexus 3264Q, 64 x 40-Gb 2 x 10-Gb SFP+, 2-RU switch

1

Table 11 Cisco Nexus 3164Q Switch Hardware

Product ID

Hardware

Quantity

N3K-C3164Q-40GE

Cisco Nexus 3164Q, 64 x 40-Gb SFP+, 2-RU switch

1

Table 12 Cisco Nexus 31128PQ Switch Hardware

Product ID

Hardware

Quantity

N3K-C31128PQ-10GE

Nexus 31128PQ, 96 x 10 Gb-SFP+, 8 x 10-Gb QSFP+, 2-RU switch

1

Supported Optics

To determine which transceivers and cables are supported by this switch, see https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-device-support-tables-list.html.

To see the transceiver specifications and installation information, see https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-installation-guides-list.html.

Supported FEX Modules

Cisco NX-OS Release 7.0(3)I6(2) supports the following FEXes (Fabric extenders) on 93180YC-EX, 9332PQ, 9372PX, 9372PX-E, 9396PX, 93108TC-EX, 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 2348TQ-E

■      Cisco Nexus 2348UPQ

■      Cisco Nexus B22Dell

■      Cisco Nexus B22HP

■      Cisco Nexus NB22FTS

■      Cisco Nexus NB22IBM

■      For more information, see the Cisco Nexus 9000 Series Switch FEX Support page.

■

Note: Please note the following:

■      The N9K-X9408PC-CFP2 line card does not support the Cisco Nexus 2300 platform FEXs.

■      Cisco Nexus 9300 platform switches do not support FEXs 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 Nexus 2248PQ, 2348TQ, and 2348UPQ FEXes support connections to the Cisco Nexus 9300 or 9500 platform switches by using supported breakout cables to connect a QSFP+ uplink on the FEX and an SFP+ link on the parent switch (4x10 G links).

Note: For Cisco Nexus 9500 platform switches, 4x10-Gb breakout for FEX connectivity is not supported.

■      The 93180LC-EX only supports the following FEXes only on down links (1-27):

o    Cisco Nexus 2348TQ

o    Cisco Nexus 2348TQ-E

o    Cisco Nexus 2348UPQ

New and Changed Information

This section lists the following topics:

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

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

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

Cisco NX-OS Release 7.0(3)I6(2) does not include new hardware features.

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

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

Layer 2 Switching Features

■      The mac-address bpdu source version 2 command enables STP to use the new Cisco MAC address (00:26:0b:xx:xx:xx) as the source address of BPDUs generated on vPC ports.

For more information, see the  Cisco Nexus 9000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x.

Caveats

This section includes the following topics:

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

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

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

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

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

Table 13 Resolved Caveats in Cisco NX-OS Release 7.0(3)I6(2)

CSCuu58215

Nexus 9396 should be reloaded when all the internal hg links are down

CSCux85700

Accounting logs become unusable/CPU spike with NFM

CSCva90112

:7.0(3)I2(2a):9372PX - "FEX" crash on N2K-B22IBM-P

CSCvb66783

N9k - kernel I/O error / copy run start fails - Bootflash goes readonly

CSCvb78782

N9K: Control plane protocol packet observed at ethanalyzer and not delivered to process

CSCvd62161

Need option to use kstack for file transfers

CSCvd70599

QSFP-40G-SR4-S / QSFP-100G-SR4-S: show int eth x/y trans not showing correct PID

CSCvd90825

Static NAT stops working after reload or reconfiguring NAT statement if SVI is NAT inside interface.

CSCvd99364

Non Cisco MAC address used for BPDUs sent on vPCs - porting to N3K/N9K

CSCve03760

ACE's insertion  in ACL is failing

CSCve06744

N9K: vPC peer-keepalive fails after initial mis-config and cannot save config

CSCve11958

N9000 drops transit BFD packets when acting as L2 switch with SVI

CSCve17293

Policy-map with description cannot be applied to service-policy

CSCve26876

N9k - VXLAN - FL - DHCP NAK packet causes mac flap with DHCP relay enabled

CSCve29909

Stale next-hop in FIB following l2route update in VXLAN EVPN

CSCve31661

"no lacp suspend-individual" configured on NIF results in HIF ports don't work

CSCve34475

config sync buffer does not clear after commit

CSCve36588

ACL under mgmt0 interface of N9k not denying icmp packets with timestamp-request

CSCve38036

3k/9k - when using telnet connection to pass CLI commands in Python cli.cli("show command") may hang

CSCve46142

No control/data packets Tx after "%-SLOT1-3-BUFFER_THRESHOLD_EXCEEDED:" message for 200%+ usage

CSCve47885

Cap the size nxapi-server logs can grow to in /volatile

CSCve51590

Sflow TS missing data required for serviceability

CSCve55721

BGP update not sent out when advertisement-interval is configured

CSCve56535

wget under bash-shell cannot find root CA certificate

CSCve58719

Module Serial number instead of Switch serial number in OF statistics

CSCve58988

Stale /32 host route after route flap

CSCve59930

G-3/13/34: Seeing FEX--1 initiating shutting down in 60s due to fan failure---for both PQ fexes

CSCve60078

Device in NDB becomes suddenly disconnected - nginx_f crash

CSCve60274

Fix BFD transit issue

CSCve65062

N3232C unexpected sporadic high PTP corrections

CSCve65378

Switch-profile import verify fails for "no lacp suspend-individual"

CSCve66635

marker-packet interval is not working proper

CSCve67787

Static NAT outside forward not working

CSCve67821

Session manager does not work for egress ACL

CSCve67933

BFD casued control QoS group drop on N93180YC-EX

CSCve69009

bcm-usd crash in soc_mem_alpm_insert

CSCve72947

N9396 ERSPAN market packet indicates incorrect clock granularity

CSCve73433

DOT1q VLAN not programmed after ISSU from 7.0(3)I5(2) to 7.0(3)I6(1)

CSCve74904

nginx crash

CSCve75312

NETCONF native vlan config abnormal

CSCve75813

SB-Getting an error "Interface not present in ObjectStore" after changing fex id

CSCve76686

N9500/9432PQ-Need syslog reporting uncorrectable parity error on BCM followed by reload of LC.

CSCve78733

CLI yields strange output - " Message reported by command ::     config terminal "

CSCve78998

XMLSA process crash after memory exhaustion

CSCve80495

Add "show interface hardware-mapping" to show tech detail output

CSCve82514

Link not connected after OIR QSA+1G SX on N9K-C9236C re-timer ports

CSCve82663

default interface command may modify startup-config without user awareness

CSCve84191

Trap extended-linkDown/extended-linkUp not sent when interfaces goes down/up.

CSCve85825

Static mac insert failed for custom router mac

CSCve86603

n9k as-override no work after reload with maintenance mode

CSCve87784

BGP Process Crash when receivng AS Path longer than 255

CSCve91311

OSPF Area Range Command Truncated

CSCve93699

Syslog of constantly corrected parity errors

CSCve95676

N9k/ "ntp access-group" missing from config after upgrade to 7.0(3)I6(1)

CSCvf03126

FHRP VMAC is not learned dynamically over overlay(F&L VXLAN) in software

CSCvf03227

N9k - Auto negotiation status not reflected correctly in show interface output

CSCvf05256

switchport is stuck into "trunk" (inherited) mode after port-profile de-inheritance

CSCvf07749

FM reloaded due to not responding on EOBC path

CSCvf08218

HIF bring up slow after FEX online

CSCvf11082

Nexus 9508 management port LEDs do not work properly

CSCvf13949

libfcoe.log file getting populated causing Python crashes

CSCvf21964

N9k - packets hitting inband and not going through span rate-limiter when span acl is used

CSCvf23136

LC ipfib memory leak on 93180YC-EX

CSCvf25461

vPC interface down with reason vPC peerlink down.

CSCvf29539

Flood & Learn VXLAN: Traffic looped between Non-VPC VTEP and SPINE on SVI uplink

CSCvf31571

Snmpbulkwalk slowness observed in ieee802SecyMIBs.

CSCvf36182

After adding new VLAN to VLAN DB, native VLAN connectivity fails on trunk

CSCvf36441

Traceroute - ICMP TTL exceed message sourced from wrong interface

CSCvf40773

Configuration Won't Apply To FEX Ports After Upgrade

CSCvf46708

N9K -- json output permissions failing on user with custom role

CSCvf46731

During Upgrade from I4.5 to I4.6. The VPC legs did not come up on VPC secondary.

CSCvf50425

VxLAN Overlay PIM packets (Register & Register-Stop)  gets dropped on 40Gig uplink ports

CSCvf51396

lldp tlv-set configuration not retained inside port-profile

CSCvf56928

N9K/openflow: redirect port bitmap is not updated when port-channel member comes up

CSCvf57890

RACL doesn't get programmed in the hardware for VXLAN VLAN without a member port

CSCvf59161

N9K vPC ERSPAN down // destination reachable via peer-link

CSCvf59623

Disable C-state for LC/FC based on Intel Atom based CPU

CSCvf59686

Clicking ejector handle causes OS print "Ejector pulled (left/right) for LC" messages continuously

CSCvf66895

Do not allow 'default interface' cli on an interface (error out), when speed group .. is configured

CSCvf70482

Storm control policer became 0x0 and interface locked after many interfaces and remote-flap, 9300-EX

CSCvf71809

Link flap observed on port on X97xx line card if it  matches the same src port/slice for bad port

CSCvf77259

Line vty session limits does not work as expected with port-profile configurations present on N9k

CSCvf80237

Port VLAN mapping is broken on egress for ingress routed traffic

CSCvf86285

Switch sends different vlan IPv6 RA on a fex access port

CSCvf86455

BGP locally originated path becomes invalid

CSCvf89022

Bulk vlan name configuration causes MTS backup

CSCvf94030

N9K:PBR with multiple "set ip next-hop verify-availability [next hop] track #" not work

CSCvg01785

N9K Connection to DWDM Carrier held down

CSCvg04522

Corrupted packets causing traffic looping between LC and FM on 9516

CSCvg04877

F&L: NVE peer not formed after VTEP reload

CSCvg05807

N9K: IOS attached VPCs err-disabled during upgrade to 7.0.3.I6.1 or newer

CSCvg07375

IR EVPN: BUM traffic gets dropped on ingress Leaf after route change in Underlay

CSCvg16197

N9k -EX all interface counters stop incrementing

CSCvg19941

VXLAN - L3 Point-to-Multipoint Uplink support on 9200/9300-EX

CSCvg24055

TAHUSD crash with a HAP failure on on Nexus 9K

CSCvg26718

BGP routes imported into RIB more than maximum path set

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

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

Table 14 Open Caveats in Cisco NX-OS Release 7.0(3)I6(2)

Bug ID

Description

CSCuy08187

If EPLD is not latest, terminate non-disruptive ISSU

CSCvg14780

VTY ACL not programmed in hardware after ISSU - NXOS I4(6) -> I6(1)

CSCvg24680

SNMP config fails for aaa remote user over NXAPI REST

CSCvg29889

eVPN : randomly SVI interface is not configured.

CSCvg33127

Nexus broker switches disappears periodically in the NDB topology

CSCvg33622

SFP-10G-SR-S incorrectly display copper length, uses udld copper default and syntax [no] udld enable

CSCvg34032

'not enough memory' reported when modifying a policy-map or a related class-map / ACL

CSCvg34748

N9K USB not detected after OIR

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

Table 4 Known Behaviors in Cisco NX-OS Release 7.0(3)I6(2)

Bug ID

Description

CSCvc95008

On Cisco Nexus 9300-EX switches, when 802.1q EtherType has changed on an interface, the EtherType of all interfaces on the same slice will be changed to the configured value. This change is not persistent after a reload of the switch and will revert to the EtherType value of the last port on the slice.

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)I6(2).

■      IPv6 multicast is not supported on Cisco Nexus 9500 platform switches.

■      If you are upgrading from Cisco NX-OS Release 7.0(3)I5(2) to Cisco NX-OS Release 7.0(3)I6(2) and Straight Through FEX with vPC is shut, VXLAN virtual ports are not created for that port channel. When the upgrade to Cisco NX-OS Release 7.0(3)I6(2) is complete, missing VXLAN virtual ports cause MAC deletion.

■      SFP management port on the 93180LC-EX line card is not supported.

■      Line rate cannot be sustained across all 36 ports on the 9736C-EX line card.

■      You must use either the CLI or SNMP to configure a feature on your switch. Do not configure a feature using both interfaces to the switch.

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

■      Q-in-VNI has the following limitations:

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

switch(config)# int nve 1

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

switch # 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.

¯    Double tag is not supported on Cisco Nexus 9300-EX platform switches, only single tag is supported.

¯    When upgrading from Cisco NX-OS Release 7.0(3)I3(1) or 7.0(3)I4(1) to Cisco NX-OS Release 7.0(3)I6(2) with Cisco Nexus 9300 platform 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 NX-OS Release 7.0(3)I3(1) and 7.0(3)I4(1). We now support single tag also in Release 7.0(3)I6(2).

¯    We do not support traffic between ports configured for Q-in-VNI and ports configured for trunk on Cisco Nexus 9300-EX platform switches.

■      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)I6(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 platform switch that is running Cisco NX-OS Release 7.0(3)I6(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 switches except for the 100 Gb 9408PC line card and the 100 Gb 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.

■      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 QSFP to SFP/SFP+ Adapter (40 Gb to 10 Gb):

¯    N9K-C93120TX

¯    N9K-C93128TX

¯    N9K-C9332PQ

¯    N9K-C9372PX

¯    N9K-C9372PX-E

¯    N9K-C9372TX

¯    N9K-C9396PX

¯    N9K-C93108TC-EX

¯    N9K-C93180YC-EX

■

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

■      Only 10 Gb can be supported using the QSFP-to-SFP Adapter on 40-Gb uplink ports on Cisco Nexus 9300 platform switches in NX-OS.

■      1 Gb with QSFP-to-SFP Adapter is not supported.

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

■      All ports in the QSFP-to-SFP Adapter speed group must operate at the same speed (see the configuration guide).

■

■      The following switches support the breakout cable (40 Gb ports to 4x10-Gb ports):

¯    N9K-C9332PQ

¯    N9K-X9436PQ

¯    N9K-X9536PQ

¯    N9K-C93180LC-EX—last four ports are breakout capable (10x4, 24x4, 50x2)

¯    N9K-C93180YC-EX

¯    N9K-C93108TC-EX

¯    N9K-X9732C-EX line card

¯    N9K-X97160YC-EX

■      Weighted ECMP (Equal-Cost Multi-Path) Cisco Nexus 3000 Series 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

For more information, see the Cisco Nexus 9000 Series NX-OS Layer 2 Switching Configuration Guide.

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.

■      PVLANs 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 vlan command.

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

■      PVLANs 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)

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

■      PVLANs support STP as follows:

¯    MST (Multiple Spanning Tree)

¯    RSTP (Rapid Spanning Tree Protocol)

■      PVLANs port mode is not supported on the following:

¯    40-Gb interfaces of the Cisco Nexus ALE ports on Cisco Nexus 9300 platform switches.

¯    Cisco Nexus 3164Q

■      PVLANs are supported on breakout ports for the Cisco Nexus 9200 and 9300-EX platform switches.

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

■      Breakout ports cannot be configured to be part of a private VLAN on Cisco Nexus 9500 platform switches’ 40 G ports with the following line cards:

o    N9K-X9636PQ

o    N9K-X9564PX

o    N9K-X9564TX

o    N9K-X9536PQ

o    N9K-X9432PQ

o    N9K-X9464PX

o    N9K-X9464TX

■      For more details, see the Cisco Nexus 9000 Series NX-OS Layer 2 Switching 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 PVLANs.

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

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

■      For PVLAN 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 PVLAN ports configured to a release that does not support PVLAN 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 PVLAN configuration causes PVLAN 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 PVLAN configuration. Layer 2 trunk interfaces, which may carry PVLANs, are active and remain part of the STP database.

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

Limitations with Other Features

Consider these configuration limitations with other features when configuring PVLAN:

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 PVLANs, STP controls only the primary VLAN.

■      PVLAN host or promiscuous ports cannot be SPAN destination ports.

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

Guidelines and Limitations for Fabric Extenders

This section list configuration guidelines and limitations for the Cisco Nexus 2000 Series Fabric Extenders:

■      Post-routed flood is not supported.

■      The configuration is purged when:

o    Straight-through FEXes are converted to dual-homed

o    Dual-homed FEXes are converted to Straight-through.

■      Conversion from dual-homed FEX to straight-through or straight-through to dual-homed FEX requires a reload of the parent switch.

There are two cases for dual-home to straight-through conversion:

■      While the FEX is online: the FEX goes down as a dual-homed FEX on conversion and comes back up a straight-through FEX. The configuration is purged on bringup.

■      While the FEX is offline: the FEX goes down as a dual-homed FEX, then the no vpc id command is entered on the fabric port channel.  No configuration purge takes place. In this scenario, default the configuration on FEX interfaces while toggling the mode from active-active to straight-through.

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

Unsupported Features

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

§  Cisco Nexus 3232C and 3264Q Switches

§  Cisco Nexus 9200 and 9300-EX Series Switches

§  Cisco Nexus 9408 Line Card and 9300 Series Switches

§  Cisco Nexus 9732C-EX Line Card

§  DHCP

§  FEX

§  Other Unsupported Features

§  PVLAN

§  VXLAN

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 NX-OS image from the loader.

■      Automatic negotiation support for 25-Gb and 50-Gb 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)

■      Enhanced ISSU. NOTE: Check the appropriate guide to determine which platforms support Enhanced ISSU.

■      MLD

■      PIM6

■      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 platform switches or between Cisco Nexus 3232C or 3264Q switches and Cisco Nexus 3100 Series switches

■      VXLAN IGMP snooping

Cisco Nexus 9200 and 9300-EX Platform Switches

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

■      64-bit ALPM routing mode

■      Cisco Nexus 9272PQ and Cisco Nexus 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

■      Egress port ACLs

■      Egress QoS policer or marking

■      FEX (supported for Cisco Nexus 9300-EX platform switches but not for Cisco Nexus 9200 platform switches.)

■      GRE v4 payload over v6 tunnels

■      Host to LPM spillover

■      IP length-based matches

■      IP-in-IP on Cisco Nexus 92160 switch

■      ISSU enhanced

■      Layer 2 Q-in-Q is supported only on Cisco Nexus 9300-EX platform switches (93108TC-EX and 93180YC-EX) and Cisco Nexus 9500 platform switches with the X9732C-EX line card.

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

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

■      PV routing for VXLAN

■      PVLANs (supported on Cisco Nexus 9300 and 9300-EX platform switches but not on Cisco Nexus 9200 platform switches)

■      Q-in-VNI is not supported on Cisco Nexus 9200 platform switches. Beginning with Cisco NX-OS Release 7.0(3)I5(1), Q-in-VNI is supported on Cisco Nexus 9300-EX platform switches.

■      Q-in-Q for VXLAN is not supported on Cisco Nexus 9200 and 9300-EX platform switches

■      Q-in-VNI is not supported on Cisco Nexus 9200 platform switches (supported on Cisco Nexus 9300-EX platform switches)

■      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

■      SVI uplinks with Q-in-VNI are not supported with Cisco Nexus 9300-EX platform switches

■      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 9500 Platform N9K-X9408PC-CFP2 Line Card and 9300 Platform Switches

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

■      802.3x

■      Breakout ports

■      FEX (this applies to the N9K-X9408PC-CFP2 and –EX switches, not all Cisco Nexus 9300 platform switches)

■      MCT (Multichassis EtherChannel Trunk)

■      Only support 40G flows

■      Port-channel (No LACP)

■      PFC/LLFC

■      PTP (Precision Time Protocol)

■      PVLAN (supported on Cisco Nexus 9300 platform switches)

■      Shaping support on 100g port is limited

■      SPAN destination/ERSPAN destination IP

■      Storm Control

■      vPC

■      VXLAN access port.

N9K-X9732C-EX Line Card

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

■      FEX

■      IPv6 support for policy-based routing

■      LPM dual-host mode

■      SPAN port-channel destinations

■      TAP aggregation

DHCP

DHCP subnet broadcast is not supported.

FEX

■      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 platform switches do not support FEX on uplink modules (ALE).

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

■      FEX vPC is not supported between any model of FEX and the Cisco Nexus 9500 platform switches as the parent switches.

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

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

■      FEX Layer 3 is not supported on the Cisco Nexus 2348TQ-E fabric.

Other Unsupported Features

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

■      Cisco Nexus 9300 platform 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 40-Gb physical ports on the Cisco Nexus 9372PX, 9372TX, and 9332PQ switches

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

PVLAN

This section lists PVLAN features that are not supported.

·       PVLAN PO/VPC PO is not supported on Cisco Nexus N9K-X9632PC-QSFP100, N9K-X9432C-S.

VXLAN

This section lists VXLAN features that are not supported.

■      Consistency checkers are not supported for VXLAN tables.

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

■      IPv6 for VXLAN EVPN ESI MH is not supported.

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

■      QoS classification is not supported for VXLAN traffic in the network-to-host direction as ingress policy on uplink interface.

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

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

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

Related Documentation

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

https://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:

https://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:

https://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:

https://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

The Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference is available at the following URL:

https://developer.cisco.com/site/nx-os/docs/n3k-n9k-api-ref/

New Documentation

The Cisco Nexus 9000 Series and Cisco Nexus 3000 Series FPGA/EPLD Upgrade Release Notes, Release 7.0(3)I6(2) is available at the following URL.

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/epld_rn/guide/nxos_epldRN_703i61.html

The Cisco Nexus 9000 Series NX-OS Verified Scalability Guide, Release 7.0(3)I6(2) is available at the following URL:

https://www-author.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I61/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I61.html

The Cisco Nexus 93180LC-EX NX-OS Mode Hardware Installation Guide is available at the following URL:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/hw/n93180lcex_hig/guide/b_c93180lcex_nxos_mode_hardware_install_guide.html

The Cisco Nexus 92300YC NX-OS Mode Hardware Installation Guide is available at the following URL:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/hw/n92300yc_hig/guide/b_c92300yc_nxos_mode_hardware_install_guide.html

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:

https://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)I6(2)

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