Cisco Nexus 3000 Series NX-OS Release Notes, Release 7.0(3)I7(8)

This document describes the features, issues, and limitations of Cisco NX-OS Release 7.0(3)I7(8) software for use on Cisco Nexus 3000, 3100, 3200 and 3500 switches. For more information, see Related Documentation.

Note: The Cisco Nexus 3400-S and 3600 platform switches are not supported in Cisco NX-OS Release 7.0(3)I7(8). Starting with Cisco NX-OS Release 7.0(3)I2(1), the Cisco NX-OS image filename has changed to start with "nxos" instead of "n3000."

Table 1 Online History Change

Date

Description

Jan 18, 2021

Updated the Upgrade and Downgrade section for Compact NX-OS Image.

March 04, 2020

Created the release notes for Cisco NX-OS Release 7.0(3)I7(8).

Contents

■      New Software Features

■      New Hardware Features

■      Open Issues

■      Resolved Issues

■      Known Issues

■      Device Hardware

■      Upgrade and Downgrade

■      MIB Support

■      Unsupported Features

■      Supported Optics

■      Related Documentation

■      Documentation Feedback

■      Obtaining Documentation and Submitting a Service Request

New Software Features

Table 2: New Software Features

Feature

Description

Pre-compacted NX-OS Images

Cisco Nexus 3048, 3064, 3132 (except for the N3K-C3132Q-V), and 3172 platform switches with a model number that does not end in -XL must run a “compact” NX-OS software image due to limited bootflash space. This “compact” image can be created using the NX-OS Compact Image procedure; alternatively, a compact NX-OS software image can be downloaded directly from Cisco's Software Download website. This requirement does not apply to any other model of Cisco Nexus 3000 or 3100 series switch. This requirement does not apply to the Nexus 3132Q-V switch.

For more information, see the following documents:

·       “Upgrade and Downgrade” section in this document.

·       Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x

Syslog messages to account packet drops

Support to enable syslog messages to account packet drops on multicast queues for no-drop class on all Cisco Nexus 3000 and 3100 Series Switches except Cisco Nexus C3132Q-V, C31108PC-V, C31108TC-V and C3132C-Z switches.

For more details, see the Cisco Nexus 3000 Series NX-OS QoS Configuration Guide, Release 7.x

Redirect control plane packets for OpenFlow ports

Support to enable forwarding of control plane link-level PDUs to OpenFlow redirect ports matching flows on Cisco Nexus 3500 switches.

For more details, see the Cisco OpenFlow Agent for Nexus 3000 and 9000 Series Switches

Enabling syslog messages to account link level pause frames

Support to enable syslog messages to account all the incoming global and link level pause frames.

For more details, see the Cisco Nexus 3000 Series NX-OS QoS Configuration Guide, Release 7.x

New Hardware Features

Table 3: New Hardware Features

Feature

Description

QSFP-100G-FR-S

Added support for QSFP-100G-FR-S (100GBASE FR QSFP Transceiver) for Cisco Nexus C3232C platform switches. For more details, see the Transceiver Module (TMG) Compatibility Matrix.

Open Issues

The following tables lists the Open Issues in Cisco Nexus 3000, 3100, 3200 and 3500 Series switches in Cisco NX-OS Release 7.0(3)I7(8). Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.

■      Open Issues in Cisco Nexus 3000, 3100 and 3200 Switches

■      Open Issues in Cisco Nexus 3500 Switches

Table 4: Open Issues in Cisco Nexus 3000, 3100, 3200 Series Switches

Bug ID

Description

CSCvq96790

Headline: OSPF single hop BFD is not working on specific platforms

Symptom: BFD sessions where peers are connected via intermediate hop Nanook switch may not come up. This is due to Nanook punting transit BFD packets to SUP instead of forwarding them.

Workaround: No BFD should be configured on Nanook device when acting as intermediate hop switch. If BFD is required on intermediate hop switch due to other connectives/applications, no workaround exists.

Table 5: Open Issues in Cisco Nexus 3500 Series Switches

Bug ID

Description

CSCvq98238

Headline: Multicast UDP NAT support is not available on Cisco Nexus 3500 Switches

Symptom: Multicast NAT UDP based translation won't happen. Only Multicast NAT based on source IP & destination IP is current supported but not based on UDP port.

Workaround: Multicast NAT with only source IP or destination group must be used in translation.

CSCvq60625

Headline: Cannot apply ERACL on PO sub interfaces

Symptom: When you configure ERACL on a PO sub-interface, the policies are not applied and/or programmed in the hardware.

Workaround: No workaround.

Resolved Issues

The following tables list the Resolved Issues in Cisco Nexus 3000, 3100, 3200 and 3500 Series switches in Cisco NX-OS Release 7.0(3)I7(8). Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.

■      Resolved Issues in Cisco Nexus 3000, 3100 and 3200 Switches

■      Resolved Issues in Cisco Nexus 3500 Switches

Table 6: Resolved Issues in Cisco Nexus 3000, 3100, 3200 Series Switches

Bug ID

Description

CSCvp41943

Headline: Cisco Nexus 3000, 3100 and 3200 series switches may experience permanent PTP high correction

Symptom: Constantly high PTP correction (~125/250ms) with no change in the grandmaster clock.

Workaround: No workaround. To clear the condition power cycle the impacted device.

CSCvq83081

Headline: Links on ports 14 and 15 on Cisco Nexus C9332PQ devices,  goes down with QSA+ 10G transceiver

Symptom: We have two pairs of Cisco Nexus 9000 switches. Each pair is in vPC and back to back vPC is configured between the two pairs. When we removed 40G SFP on an interface which is not a part of vPC and replaced it with 10G SFP, we see that the vPC port-channel between the two pairs goes down.

Workaround: Port 13 and 14 on N9K-C9332PQ do not support 4x10G breakout and therefore QSA+10G is also not supported. But having QSA+10G causes link issue on neighbor ports. Avoid using QSA+10G transceivers on port 13 and 14.

CSCvr04588

Headline: Cisco Nexus 3100-V Buffer Wedge/Lockup: All Control-Plane Protocols Failing and Ports Unable to Pass Traffic

Symptom: A Nexus 3100-V Series Switch may experience a condition in which the ingress/egress buffers become "stuck" (unable to dequeue frames).  This will lead to a condition where, depending on the specific queue experiencing the issue, all traffic may fail to pass in or out of the devices.  Common symptoms will be failure of all control-plane protocols, input or output discards on multiple/all interfaces, RewriteEngineLoopback diagnostic failure, and low to near-zero ingress/egress utilization on impacted interfaces. This condition is seen on software release 7.0(3)I7(6).  If similar symptoms are seen on an earlier software release, contact Cisco TAC to determine if conditions match a different defect.

Workaround: Reload the impacted device.

CSCvr25215

Headline: Cisco Nexus C3164Q devices with 40GE displays an error and reboots at higher Cisco NX-OS versions

Symptom: Cisco Nexus 3000, 3100 switches and 1st generation Cisco Nexus 9300 switches reboot automatically on high occurrence of 2-bit parity errors (BCM_UNCORRECTABLE_PARITY_ERR) that are not correctable in its internal tables. Parity errors happen due to unpredictable hardware conditions. When this condition happens, a syslog gets printed and the switch reboots.

Workaround: None

CSCvr39951

Headline: Cisco Nexus 3000 Switches upgraded to Cisco NX-OS Release 7.0(3)i7(7) dropping to switch boot after reloading for upgrade.

Symptom:  When upgrading with compact or full image on N3K-C3172 or N3K-C3132 to 7.0(3)i7(7), after required reload for the upgrade the N3k comes up in switch boot prompt. After gaining local access and loading 7.0(3)i7(7) from switch boot the N3k comes up in 7.0(3)i7(7). If the N3k hits the issue and is downgraded back, with BIOS also downgraded, it does not go to switch boot again when re-upgraded. We see the following error on console for the upgrades that come back up in switch boot after reloading.

Workaround: When Cisco Nexus 3000 device is reloaded for the upgrade and if it comes up in switch boot prompt, reload the system again from switch boot prompt.

CSCvr57711

Headline: Installer should abort the installation when BIOS extraction fails on Cisco Nexus 3132 devices.

Symptom:  Installer should abort the installation when BIOS extraction fails BIOS extraction fails during upgrade. Images will be upgraded according to following table:

Module       Image                  Running-Version(pri:alt)           New-Version  Upg-Required

------  ----------  ----------------------------------------  --------------------  ------------

1        nxos                              7.0(3)I7(5a)           7.0(3)I7(7)           yes

1        bios                        v4.4.0(11/06/2017)                                  no----------->New BIOS version is empty

Workaround: Issue has been addressed in 7.0(3)I7(7.37) 7.0(3)I7(7.44)

CSCvr57912

Headline: BIOS upgrade failed while performing "install all" upgrade on Cisco Nexus 3132 devices.

Symptom: BIOS upgrade failed while performing "install all" upgrade on Cisco Nexus 3132 devices

Compatibility check is done:

Module  bootable          Impact  Install-type  Reason

------  --------  --------------  ------------  ------

1       yes      disruptive         reset  default upgrade is not hitless

Images will be upgraded according to following table:

Module       Image                  Running-Version(pri:alt)           New-Version  Upg-Required

------  ----------  ----------------------------------------  --------------------  ------------

1        nxos                              7.0(3)I7(5a)           7.0(3)I7(7)           yes

1        bios                        v4.4.0(11/06/2017)                                  no--------->New-Version is missing

Workaround: Reinstall using “Install all”.

CSCvr59329

Headline: Default CoPP policy not applied after upgrade

Symptom: Cisco Nexus 3000 switch fail to apply default CoPP policy after upgrade to 7.0(3)I7(x). This result in drops of control packets.

Workaround: Run setup command to install default CoPP policy.

CSCvr60413

Headline: Spanning tree configuration disappear from show run switch profile after initial sync

Symptom:  The 'spanning tree port type' only added into switch-profile running configuration  for  vPC peer-link.  For the other link, the ' spanning tree port type' command will randomly out of sync  from at least one of the link.

Workaround: None

CSCvr76087

Headline: Crash due to high rate parity error correction

Symptom: Crash due to high rate parity error correction. USER-3-SYSTEM_MSG: EEM failed to publish event instance=0^Bmodule=1^Bdevid=241^Bdesc="correctable parity errors"^B due to high rate, rc = 0x412d0011 - t2usd

Workaround: None

CSCvr93741

Headline:  Cisco Nexus 3000 devices running 7.0(3)I4(7) and 7.0(3)I7(6) may fail with errors on ISSU

Symptom:  TORs and EOR LCs on Cisco Nexus 3000, 3100 and 3200 devices when doing an ISSU to NX-OS Images with Broadcom SDK 6.4.8 might fail in rare cases due to timeout with the following errors:

switch# slot 1 quoted "show logging onboard internal bcm-usd.

Workaround: A workaround script may reduce the probability of trigger condition. But you may not be able to avoid failure in all cases. You must use the script only under the guidance of Cisco technical support.

CSCvs09462

Headline: Incorrect license installed on Cisco Nexus 3000 Switches

Symptom: FC_PORT_ACTIVATION_PKG license was installed incorrectly

Workaround: Clear the license using the command clear license sprom and then reload the switch.

CSCvs37767

Headline: GLC-LH-SMD inside CVR-QSFP-SFP10G (QSA) inserted in Cisco Nexus 3100 switch may not come up as expected.

Symptom: When a GLC-LH-SMD 1G SFP transceiver inside of a CVR-QSFP-SFP10G (QSA) QSFP+ transceiver is inserted in a 40G QSFP+ interface of a Nexus 3100 device, the link may not reliably come up/up as expected within NX-OS. This symptom can particularly be observed after a reload of the Nexus 3100 device, although other scenarios exist where the interface may not come up as expected. The device at the remote end of the down/down link may report that the link is up/up as expected. Furthermore, the RX/ingress counters of the affected interface on the Nexus 3100 device may report that traffic is being received, while the TX/egress counters of the affected interface do not report any traffic being sent out of the link.

Workaround: +++ Bouncing the affected interface using the following configuration brings up the link:

Switch# configure terminal

Switch(config)# interface Ethernet1/49/1

Switch(config-if)# shutdown

Switch(config-if)# no shutdown

CSCvs39382

Headline: Link on Cisco Nexus 3100 device fails after inserting a CVR-QSFP-SFP10G (QSA) with GLC-LH-SMD

Symptom: When a GLC-LH-SMD 1G SFP transceiver inside a CVR-QSFP-SFP10G (QSA) QSFP+ transceiver is inserted in a 40G QSFP+ interface of a Nexus 3100 device, the link may not reliably come up/up as expected when the GLC-LH-SMD transceiver is removed, then re-inserted inside the CVR-QSFP-SFP10G. Furthermore, DOM information for the GLC-LH-SMD may not appear as expected. Specifically, the transceiver's "Current" reading may show as 0.00mA, the "Tx Power" reading may shows as N/A, and the transceiver's type may show as "Unknown Type-(unknown)".

switch# show interface Ethernet1/51/1 transceiver details

Ethernet1/51/1

transceiver is present

type is Unknown Type-(unknown)    <<<

name is CISCO

part number is SFCT-5716PZ

revision is 001

serial number is XXX

nominal bitrate is 1300 MBit/sec

Link length supported for 9/125um fiber is 10 km

cisco id is 3

cisco extended id number is 4

cisco part number is 10-2625-01

cisco product id is GLC-LH-SMD

cisco vendor id is V01

SFP Detail Diagnostics Information (internal calibration)

----------------------------------------------------------------------------

Current              Alarms                  Warnings

Measurement     High        Low         High          Low

----------------------------------------------------------------------------

Temperature   35.76 C        90.00 C    -10.00 C     85.00 C       -5.00 C

Voltage        3.34 V         3.63 V      2.97 V      3.47 V        3.14 V

Current        0.00 mA  --   65.09 mA     2.40 mA    61.00 mA       3.00 mA     <<<

Tx Power          N/A         0.00 dBm  -13.01 dBm   -3.00 dBm     -9.50 dBm    <<<

Rx Power      -5.71 dBm       0.00 dBm  -23.01 dBm   -3.00 dBm    -19.20 dBm

Transmit Fault Count = 0

----------------------------------------------------------------------------

Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning

Workaround: To proactively avoid encountering this issue, avoid removing and re-inserting the GLC-LH-SMD transceiver from the CVR-QSFP-SFP10G. To work around this issue after it has been encountered, remove the CVR-QSFP-SFP10G while the GLC-LH-SMD is still inside, then re-insert the CVR-QSFP-SFP10G while the GLC-LH-SMD is still inside. Then, administratively bounce the link as shown below:

switch # configure terminal

switch (config)# interface Ethernet1/51/1

switch (config-if)# shutdown

switch (config-if)# no shutdown

CSCvs49770

Headline: After modifying custom CoPP, ICMPv6 NS/ND dropping

Symptom: On a Nexus 3000 series switch after modifying the control-plane policing policy (CoPP) following a specific set of steps IPv6 neighbors might not form.

Workaround: Still under investigation

CSCvs54144

Headline: GARP Reply packet not copied to CPU on 100G link Eth1/49-52 on N3K-C31108PC-V

Symptom: GARP reply packet received on 100G port eth1/50, 52 is not punted to CPU, but with 40G link, it is working fine.

++ GARP request packet works fine on both links(100G, 400G)

Hw: N3K-C31108PC-V -

Sw:7.0(3)I7(7), I7.6

++ Tested on 9.2.3 code, but still not working.

++ The condition occurs in either any portmode combination.

++ GARP request packet is working fine.

Workaround: 1. Use 40G link on Eth1/49-52

2. Use GARP Request instead of GARP reply if possible ( that is coming from a host)

3. Via the bcm-shell, remove the "MyStationHit" from the "ARP Response XE ACL" rule

###

Get ACL entry for ARP response

N31108-8# show system internal access-list sup-redirect-stats | grep -i arp

2094                                ARP Request XE ACL    23900

2095                                ARP Response XE ACL    1 <===

2096                                ARP Response HG ACL for VxLAN F&L    0

Remove MyStationHit qualifier -> this will allow GARP response to hit this ACL

N31108-8#bcm-shell module 1 "fp qual 2095 delete MyStationHit?

Reinstall entry 2095

N31108-8#bcm-shell module 1 "fp entry reinstall 2095?

Table 7: Resolved Issues in Cisco Nexus 3500 Series Switches

Bug ID

Description

CSCvi93997

Headline: Cisco Nexus 3500 switches output buffer block stuck

Symptom: Output discards on multiple interfaces causing BUM (broadcast, unicast, and multicast) traffic drops.

Workaround: Reload the switch.

CSCvo71547

Headline: Cisco Nexus 3548-XL switch reloads continuously due to USD hap reset

Symptom: USD process crash causing the switch to reload.

Workaround: None

CSCvp06880

Headline: Cisco Nexus 3500 switches drop packets when refreshing NAT HW entry after sampling timeout expires

Symptom: NAT TCP flow may experience TCP retransmission and low performance

Workaround: Use static NAT or increase sampling-timeout to be longer that time it takes for NAT TCP flow to finish.

CSCvq97992

Headline: Cisco Nexus 3500 Switches: PIM-BiDir MFDM-2-MFDM_UNSUPPORTED_BIDIR_GROUP_RANGE

Symptom: MFDM-2-MFDM_UNSUPPORTED_BIDIR_GROUP_RANGE error will be generated and multicast traffic is not forwarded correctly on source only branch

Workaround: Configure >=24 group list for PIM BiDir RP

CSCvr16876

Headline:  SNMP Polling for output discards not reporting

Symptom:  When polling output discards value via SNMP it reports all zero's though there is legitimate value

Cli <<

F340-21.09-3548P-10GX-3# show interface ethernet 1/5 | in discard

0 input with dribble  0 input discard

0 lost carrier  0 no carrier  0 babble  10105321927 output discard

JASGARRE-M-84B7:~ jasgarre$ snmpwalk -v 2c -c TEST 10.122.176.69 1.3.6.1.2.1.2.2.1.19

IF-MIB::ifOutDiscards.83886080 = Counter32: 0

IF-MIB::ifOutDiscards.151060481 = Counter32: 0

IF-MIB::ifOutDiscards.151060490 = Counter32: 0

IF-MIB::ifOutDiscards.436207616 = Counter32: 0

IF-MIB::ifOutDiscards.436211712 = Counter32: 0

IF-MIB::ifOutDiscards.436215808 = Counter32: 0

IF-MIB::ifOutDiscards.436219904 = Counter32: 0

Workaround: None

CSCvr26092

Headline:  Cisco Nexus 3500 switch ACL match counters will not increment as expected on NAT interface

Symptom: Match counters for ACL applied on NAT interface will not increment. Match counters may also change abruptly..

Workaround: None

CSCvr35608

Headline:  show system internal access-list does not show range information

Symptom: A Cisco Nexus 3500 switch running I7 code might not show the correct statistics when you have an access-list configured with statistics per-entry and layer four port ranges.

Workaround: None

CSCvr45796

Headline:  SNMP traps truncating if alias to 64 chars on Cisco Nexus 3500 Switches

Symptom:  Cisco Nexus C3548P-10GX device running 7.0(3)I7(6)

+ SNMP traps that use ifalias are sent with a maximum length of 64 bytes.

+ snmpalk for ifalias OIDs return full length (up to 255 bytes)

Workaround: None

CSCvr57751

Headline:  Input errors: SNMP walk poll MIB 1.3.6.1.2.1.2.2.1.14 returns 0

Symptom: Observed on Nexus N3K-C3548P-10GX with input errors/ Rcv-Err

Workaround: None

CSCvr66098

Headline:  Fail to break-in ports on Cisco Nexus 3500 switches

Symptom: When trying to use a break-in configuration (e.g. taking 4 x 10 Gbps and combining to 40 Gbps). We are seeing failures when using a mix of different manufacturer transceivers (Cisco based: Avago/Finisar/Oplink/Accelink). This results in the interface stay down with error sfpAbsent after bundling the interfaces with "speed 40000" configuration and the log below will be generated:

<pre> `show logging log` 2019 Sep 16 06:28:38 SWITCH_A %USER-2-SYSTEM_MSG: USD:neutron_usd_uc_xcvr_fcot_chk_port_state_40g:1782: port 42 SFP is of different type at "Link length support for copper" 0x28 vs 0x0 - neutron_usd _uc </pre>

Workaround: Currently the only workaround is to use transceivers that all share the same value for "length". This can be inspect using the following command:

<pre>

! Where 'x' = front panel port number

!

! Here we inspect the value of "Link length supported for copper is" and ensure all transceivers

! to be bundled share a matching value for length.

!

show hardware internal neutron-usd-uc xcvr fcot-info x | i i copper

</pre>

OR

<pre>

! Where 'x' is the module number

! Where 'y' is the port number

! e.g. ethernet1/1

!

! Here we inspect the value of "Link length supported for copper is" and ensure all transceivers

! to be bundled share a matching value for length.

!

show int ethernet x/y transceiver details

</pre>

CSCvr84270

Headline:  Cisco Nexus 3500 Switches shutting down SVI breaks peer-gateway results traffic blackholing

Symptom: When shutting down SVI on vPC peers, traffic is sent out via peer-link and then drop by the vPC loop avoidance.

Workaround: Create a dummy SVI and then perform a shut or no shut.

CSCvs13353

Headline: 10G link not coming up after changing transceiver from 1G to 10G

Symptom: After changing transceiver from 1G to 10G, the link does not come up.

Connections: N3K-C3548P-10GX <----------------------->N3K-C3048TP-1GE

When transceivers are swapped from an 1000base SFP to an 10Gbase-SR SFP, link does not come up.

Either Link of status will be "(linkFlapErrDisabled)" or  (Link not connected).

1)  Set manual speed 1000 with 1G SFP. (port is up and running here)

2)  Swapped with 10G SFP, link goes down.

3)  Tried to change speed to auto and manual to 10G as well, port won't come up.

4)  Tried to shut/no shut didn't work.

5)  Tried to default interface config, didn't work, port remains still down.

Above steps are performed on both switches N3K-C3548P-10GX ß---àN3K-C3048TP-1GE simultaneously.

Tested with 6.0(2)A8(3), 6.0(2)A8(11), 7.0(3)I7(6) and 9.3(2) code, same issue seen.

Workaround: [+]  Remove 1G SFP from the devices.

[+]  Change speed of the interface to auto or manual to 10G.

[+]  Reload the switches.

[+]  Insert 10G SFP at both ends.

CSCvs39335

Headline:  Layer 3 LTL index may be incorrectly programmed for valid OIF interface on Cisco Nexus 3500 devices

Symptom:  Multicast traffic does not flow after device reload.

Workaround: None

CSCvs45104

Headline: Interface remain down after errdisable auto-recovery

Symptom:  Interface will remain down as 'link not connected' after err-disable auto-recovery has removed the state of errdisable.

Workaround: apply 'shutdown' and then 'no shutdown' under the affected interface to bring it back up.

CSCvs63415

Headline: An ARP packet on a Cisco Nexus 3548P switch cannot punt to CPU after configuring IP DHCP relay address on SVI

Symptom:  An ARP packet on a Cisco Nexus 3548P switch cannot punt to CPU after configuring IP DHCP relay address on SVI

Workaround: None

CSCvg36151

Headline: QoS: qosmgr-no such PSS key error on LLFC configuration

Symptom:  Following QOS related log may be seen on Nexus 3500 series: IPQOSMGR-4-QOSMGR_LC_ERROR_MSG: Linecard 1 returned an error: no such PSS key

Workaround: None

CSCvs97553

Headline: ARP Cannot be punt to CPU after some link state change

Symptom:  In warp/normal mode, if the interface has some changes such as shutdown or unplugging the optical module, the remaining Layer 2 interfaces will fail to send ARP packets to the CPU, whether unicast ARP or broadcast ARP.

Workaround: Use static ARP

Known Issues

The following tables lists the known behaviors in Cisco Nexus 3000, 3100, 3200 and 3500 Series switches in Cisco NX-OS Release 7.0(3)I7(8). Click the bug ID to search the Cisco Bug Search Tool  for details about the bug.

Table 8: Known Behaviors in Cisco Nexus 3000 and 3100 Series Switches

Bug ID

Description

CSCvj60944

ERSPAN packets punted to CPU on ERSPAN-destination when the destination interface is down.

CSCvb33981

Cisco Nexus 3172: IPV6 ND punted to CPU even with no ipv6 configured.

CSCvg21631

N3K PBR: 'set ip default next-hop' not preferred over default route

CSCvh27369

N3K: RACL applied to SVI interface blocks L2 traffic from vPC Peer-link.

CSCvi62638

The storm control feature does not effect on the Cisco Nexus 7.x releases.

CSCvr13118

If either the show tech-support all or show tech-support details is running on the same switch at the same time, the show tech-support <component> may not collect data

Large core files are split into 3 or more files. For example:

§  1405964207_0x101_iftmc_log.3679.tar.gzaa

§  1405964207_0x101_iftmc_log.3679.tar.gzab

§  1405964207_0x101_iftmc_log.3679.tar.gzac

To decode the multiple core files, first club the files to a single file:

$ cat 1405964207_0x101_iftmc_log.3679.tar.gz* > 1405964207_0x101_iftmc_log.3679.tar.gz

Device Hardware

The following tables list the Cisco Nexus 3000 Series hardware that Cisco NX-OS Release 7.0(3)I7(8) supports. For additional information about the supported hardware, see the Hardware Installation Guide for your Cisco Nexus 3000 Series devices.

Table 9: Cisco Nexus 3000 and 3100 Series Switches

Product ID

Description

N3K-C3048TP-1GE

Cisco Nexus 3048 switch

N3K-C3064PQ

Cisco Nexus 3064 switch

N3K-C3064PQ-10GE

Cisco Nexus 3064-E switch

N3K-C3064PQ-10GX

Cisco Nexus 3064-X switch

N3K-C3064TQ-10GT

Cisco Nexus 3064-TQ switch

N3K-C31108PC-V

Cisco Nexus 31108PC-V switch

N3K-C31108TC-V

Cisco Nexus 31108TC-V

N3K-C31128PQ-10GE

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

N3K-C3132C-Z

Cisco Nexus 3132C-Z switch

N3K-C3132Q-40GE

Cisco Nexus 3132Q switch

N3K-C3132Q-40GX

Cisco Nexus 3132Q-X switch

N3K-C3132Q-V

Cisco Nexus 3132Q-V switch

N3K-C3132Q-XL

Cisco Nexus C3132Q-XL switch

N3K-C3164Q-40GE

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

N3K-C3172PQ-10GE

Cisco Nexus 3172PQ switch

N3K-C3172PQ-XL

Cisco Nexus C3172PQ-XL switch

N3K-C3172TQ-10GT

Cisco Nexus 3172TQ switch

N3K-C3172TQ-XL

Cisco Nexus C3172TQ-XL switch

Table 10: Cisco Nexus 3000 and 3100 Series Fans, Fan Trays and Power Supplies

Product ID

Description

N2200-PAC-400W

Cisco Nexus 2000 or Nexus 3000 400W AC power supply, forward airflow (port side exhaust)

N2200-PAC-400W-B

Cisco Nexus 2000 or 3000 400W AC power supply with reverse airflow (port-side intake).

N2200-PDC-400W

Cisco Nexus 2000 or Nexus 3000 400W DC power supply, forward airflow (port side exhaust)

N3K-C3048-FAN

Cisco Nexus 3048 fan module with forward airflow (port-side exhaust)

N3K-C3048-FAN-B

Cisco Nexus 3048 fan module with reverse airflow (port-side intake)

N3K-C3064-X-BA-L3

Cisco Nexus 3064-X reversed airflow (port-side intake) AC power supply

N3K-C3064-X-BD-L3

Cisco Nexus 3064-X forward airflow (port-side intake) DC power supply

N3K-C3064-X-FA-L3

Cisco Nexus 3064-X forward airflow (port-side exhaust) AC power supply

N3K-C3064-X-FD-L3

Cisco Nexus 3064-X forward airflow (port-side exhaust) DC power supply

N3K-PDC-350W-B

Cisco Nexus 2000 DC power supply with reverse airflow (port-side intake)

N3K-PDC-350W-B

Cisco Nexus 2000 or Nexus 3000 350W DC power supply, reversed airflow (port side intake)

NXA-FAN-30CFM-B

Cisco Nexus 2000 or Nexus 3000 individual fan, reversed airflow (port side intake)

NXA-FAN-30CFM-F

Cisco Nexus 2000 or Nexus 3000 individual fan, forward airflow (port side exhaust

NXA-PAC-500W

Cisco Nexus 3064-T 500W forward airflow (port-side exhaust) AC power supply

NXA-PAC-500W-B

Cisco Nexus 3064-T 500W reverse airflow (port-side intake) AC power supply

Table 11: Cisco Nexus 3200 Series Switches

Product ID

Description

C1-N3K-C3232C

Cisco Nexus 3232C switch.

N3K-C3264C-E

Cisco Nexus 3264C-E switch.

N3K-C3264Q

Cisco Nexus 3264Q switch.

Table 12: Cisco Nexus 3500 Series Switches

Product ID

Description

N3K-C3524P-10G

Cisco Nexus 3524 switch

N3K-C3524P-10GX

Cisco Nexus 3524 switch, 24 SFP+

N3K-C3524P-XL

Cisco Nexus 3524-XL switch

N3K-C3548P-10G

Cisco Nexus 3548 switch

N3K-C3548P-10GX

Cisco Nexus 3548x switch, 48 SFP+

N3K-C3548P-XL

Cisco Nexus 3548-XL switch

Table 13: Cisco Nexus 3500 Series Fans, Fan Trays and Power Supplies

Product ID

Description

N2200-PAC-400W

Cisco Nexus 2000 or Nexus 3000 400W AC power supply, forward airflow (port side exhaust)

N2200-PAC-400W-B

Cisco Nexus 2000 or Nexus 3000 400W AC power supply, reversed airflow (port side intake)

N2200-PDC-400W

Cisco Nexus 2000 or Nexus 3000 400W DC power supply, forward airflow (port side exhaust)

N3K-PDC-350W-B

Cisco Nexus 2000 or Nexus 3000 350W DC power supply, reversed airflow (port side intake)

NXA-FAN-30CFM-B

Cisco Nexus 2000 or Nexus 3000 individual fan, reversed airflow (port side intake)

NXA-FAN-30CFM-F

Cisco Nexus 2000 or Nexus 3000 individual fan, forward airflow (port side exhaust

Upgrade and Downgrade

Upgrading Cisco Nexus 3000 and 3100 Series Switches

To perform a software upgrade for Cisco Nexus 3000 and 3100 Series switches that run in N3K mode, follow the instructions in the Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x.

To perform a software upgrade for Cisco Nexus 3100 Series switches that run in N9K mode, follow the instructions in the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x.

The upgrade process is triggered when you enter the install all command. This section describes the sequence of events that occur when you upgrade a single Cisco Nexus 3000 Series switch.

Note:

§  If you have a release prior to Release 7.0(3)I2(1), upgrade to Cisco Nexus 3000 Release 6.0.2.U6(3a) first and then upgrade to Release 7.0(3)I2(1) or later releases.

Beginning with the 7.0(3)I2(1) release, kickstart and system images are no longer used to install the Cisco NX-OS software image on Cisco Nexus 3000 and 3100 Series switches. Instead, a single binary image is used (for example, nxos.7.0.3.I4.1.bin). To install the software, you would use the install all nxos bootflash:nxos.7.0.3.I4.1.bin command.

§  Upgrade Path to Cisco NX-OS Release 7.0(3)I7(8)

§  Upgrade Guidelines and Limitations

Upgrade Path to Cisco NX-OS Release 7.0(3)I7(8)

For the list of platforms and releases that support a non-disruptive In-Service Software Upgrade (ISSU) to Cisco NX-OS Release 7.0(3)I7(8), see the Cisco NX-OS ISSU Support Matrix.

The following disruptive upgrade paths are supported:

·       For Cisco Nexus 3048 Switches:

Cisco NX-OS Release 6.0(2)U5(1) > Cisco NX-OS Release 6.0(2)U6(2a) > Cisco NX-OS Release 6.0(2)U6(10) > Cisco NX-OS Release 7.0(3)I7(8)

·       For All Cisco Nexus 3000 Series switches (except Cisco Nexus 3048 Switches):

Cisco NX-OS Release 6.0(2)U5(1) > Cisco NX-OS Release 6.0(2)U6(10) > Cisco NX-OS Release 7.0(3)I7(8)

Note: Starting with Cisco NX-OS Release 7.0(3)I7(5) Release, the fast reboot feature is not supported on Cisco Nexus 3000 and 3132 switches. It will be supported only for an upgrade to the next maintenance releases

The following table shows the upgrade paths for Cisco NX-OS Release 7.0(3)I7(8) from Cisco NX-OS Release 6.0(2)U5(1) and later.

Table 14: Upgrade Paths

From

To

Limitations

Recommended Procedure

7.0(3)I2(1) or later

7.0(3)I7(8)

None

install all is the recommended upgrade method supported.

6.0(2)U6(3a)[1] and later

7.0(3)I7(8)

None

install all is the only upgrade method supported because of a BIOS upgrade requirement.

Warning: Make sure that you store the pre-Release, 6.0(2)U6(3)’s configuration file.

For more information, see the Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x.

6.0(2)U6(2a)[2] or earlier

7.0(3)I7(8)

First, upgrade to Cisco NX-OS Release 6.0(2)U6(3a) or a later release.

A Cisco Nexus 3048 switch requires an additional step when you upgrade from a software version older than Cisco NX-OS 6.0(2)U6(2), otherwise the switch can fail to boot. You must first upgrade the switch to Cisco NX-OS Release 6.0(2)U6(2a), then to Cisco NX-OS Release 6.0(2)U6(3a), and finally to Cisco NX-OS Release 7.0(3)I7(8).

install all is the only upgrade method supported because of a BIOS upgrade requirement.

For more information, see the Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x.

Upgrade Guidelines and Limitations

Follow these guidelines and limitations while upgrading to Cisco NX-OS Release 7.0(3)I7(8):

§  Cisco Nexus 3048, 3064, 3132 (except for the N3K-C3132Q-V), and 3172 platform switches with a model number that does not end in -XL must run a “compact” NX-OS software image due to limited bootflash space. This “compact” image can be created using the NX-OS Compact Image procedure; alternatively, a compact NX-OS software image can be downloaded directly from Cisco's Software Download website. This requirement does not apply to any other model of Cisco Nexus 3000 or 3100 series switch. This requirement does not apply to the Nexus 3132Q-V switch.

§  The MD5/SHA512 checksum published on Cisco's Software Download website for a compact NX-OS software image may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Compact Image procedure.

§  The only supported method of upgrading is install all from Release 6.0(2)U6(3a) or later due to the need to upgrade the BIOS. Without the Release 7.0(3)I7(8) BIOS, the 7.0(3)I7(8) image will not load.

§  The no-save option is now required to downgrade from Release 7.x to Release 6.x. The bios-force is a hidden option that is only available on Cisco Nexus 3000 Series switches that are running 7.x releases.

§  Cisco Nexus 3000 Series switches that use software versions older than Cisco NX-OS Release 5.0(3)U5(1) need to be updated to Cisco NX-OS Release 5.0(3)U5(1) before they are upgraded to Cisco NX-OS Release 6.0(2).

§  Cisco NX-OS Release 5.0(3)U3(1) does not support a software upgrade from Cisco NX-OS Release 5.0(3)U2(2c). If you want to upgrade through this path, see CSCty75328 for details about how to work around this issue.

Note: It is recommended that you upgrade to Cisco NX-OS Release 7.0(3)I7(8) by using Cisco NX-OS install procedures.

§  In Cisco NX-OS Release 6.0(2)U2(2), the default interface name in LLDP MIB is in short form. To make it long form, you must set lldp portid-subtype to 1. In Cisco NX-OS Release 6.0(2)U2(3), this behavior was reversed. The default interface name in LLDP MIB is now in long form. To make it short form, you must set lldp portid-subtype to 0.

§  If you have set lldp port-subtype to 1 and you are upgrading to Cisco NX-OS Release 6.0(2)U2(4), ensure that you set lldp port-subtype to 0.

§  While performing a non-disruptive ISSU, VRRP and VRRPV3 will display the following messages:

§  If VRRPV3 is enabled:

2015 Dec 29 20:41:44 MDP-N9K-6 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: ISSU ERROR: Service "vrrpv3" has sent the following message: Feature vrrpv3 is configured. User can change vrrpv3 timers to 120 seconds or fine tune these timers based on upgrade time on all Vrrp Peers to avoid Vrrp State transitions. – sysmgr

§  If VRRP is enabled:

2015 Dec 29 20:45:10 MDP-N9K-6 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: ISSU ERROR: Service "vrrp-eng" has sent the following message: Feature vrrp is configured. User can change vrrp timers to 120 seconds or fine tune these timers based on upgrade time on all Vrrp Peers to avoid Vrrp State transitions. – sysmgr

§  Packet loss may occur on Cisco Nexus 31108PC-V, 31108TC-V and 3132Q-V switches when they are in the default cut-through switching-mode and the default oversubscribed port mode. These packet losses are seen in hardware counters on the egress port as TERR and/or TFCS. One of the following workarounds can be implemented to address this issue without NX-OS upgrade. To view more details, see CSCvf87120.

§  Change the port mode from oversubscribed to line-rate and then reload the switch:

§  On Nexus 31108PC-V and 31108TC-V switches, change from 48x10g+6x100g to 48x10g+4x100g+2x40g.

§  On Nexus 3132Q-V switches change from 32x40g or 26x40g to 24x40g.

§  Change the switching-mode from cut-through to store-and-forward and then reload the switch.

§  An error occurs when you try to perform an ISSU if you changed the reserved VLAN without entering the copy running-config save-config and reload commands.

§  Subinterfaces cannot be used as network ports.

§  Cisco Nexus 3000-XL platforms do not support breakout using speed 10000 CLI command. Use the interface breakout module 1 port <num> map 10g-4x CLI command instead.

§  While installing the NXAPI https certificate that is present in the device, the following error message can appear if the user does not have the permission to install this certificate  (See CSCup72219): Certificate file read error.Please re-check permissions.

§  After configuring the NXAPI feature, the default http port (port 80) is still in the listening state even after we run the no nxapi http command. This results in the sandbox becoming accessible. Although the sandbox becomes accessible, HTTP requests from the sandbox to the device do not go through. Thus, the functionality is not affected. (See CSCup77051).

§  Chunking is enabled while displaying XML output for any CLI, and html tags (& lt; and & gt;) are displayed instead of < and > both on the sandbox and while running the Python script (See CSCup84801).

This is expected behavior. Each chunk should be in XML format for you to parse it and extract everything inside the <body> tag. This is done so that it can be later concatenated with similar output from all the chunks of the CLI XML output. After all the chunks are concatenated to get the complete XML output for the CLI, this complete XML output can be parsed for any parameter.

The following workaround is recommended to address this issue:

·       Concatenate the <body> outputs from each chunk

·       Replace all the html tags (& lt; and & gt;) with < and >

·       Parse for any XML tag needed

§  If you use the write erase command, you cannot view the output for the show startup feature command. To view the startup configuration, you must then use the show startup-config command. This limitation will remain until you run the copy running-config startup-config command. After that, the show startup-config feature command will display the feature-only configuration output as expected (See CSCuq15638).

§  A Python traceback is seen while running the show xml command by using the Python shell. The exception type is httplib.IncompleteRead. This happens when you use Python scripts to leverage the NXAPI for retrieving switch data through XML or JSON. You should handle the exceptions in your Python scripts (See CSCuq19257).

§  While upgrading to a new release, when you create a checkpoint without running the setup script, the checkpoint file does not contain the copp-s-mpls class. After you run the write erase command and reload the switch, the copp-s-mpls class is created when the default configuration is applied. When a rollback is done to this checkpoint file, it detects a change in the CoPP policy and tries to delete all class-maps. Because you cannot delete static class-maps, this operation fails and, in turn, the rollback also fails.

This can also happen if you create a checkpoint, then create a new user-defined class and insert the new class before any other existing class (See CSCup56505).

The following workarounds are recommended to address this issue:

§  Run setup after upgrading to a new release.

§  Always insert the new classes at the end before a rollback.

§  When both the ip icmp-errors source and ip source intf icmp error commands are configured, then the command that is configured last takes effect.

Thereafter, if the last configured command is removed, the switch does not get configured with the command that was configured first.

§  Users who upgrade to 7.0(3)I7(8) need to run the set up script if they want to enable the MPLS static or the VRRpv3 feature.

§  The following Cisco Nexus 9000 features are not supported on the Cisco Nexus 3100 Series switches in N3K or N9K mode:

§  FEX

§  Multicast PIM Bidir

§  Port VLAN (PV) switching and routing support for VXLAN

§  Auto-Config

§  Secure login enhancements:

§ Ability to block login attempts and enforce a quiet period

§ Ability to restrict the maximum login sessions per user

§ Ability to restrict the password length

§ Ability to prompt the user to enter a password after entering the username

§ Ability to hide the shared secret used for RADIUS or TACACS+ authentication or accounting

§ SHA256 hashing support for encrypted passwords

§  SHA256 algorithm to verify operating system integrity

§  Non-hierarchical routing mode

§  NX-API REST

§  Link Level Flow Control (LLFC) is not supported on Cisco Nexus 3000 series and Cisco Nexus 3100 series switches.

§  You can disable IGMP snooping either globally or for a specific VLAN.

You cannot disable IGMP snooping on a PIM enabled SVIs. The warning message displayed is: IGMP snooping cannot be disabled on a PIM enabled SVIs. There are one or more VLANs with PIM enabled

Upgrading Cisco Nexus 3500 Series Switches

Upgrade Path to Cisco NX-OS Release 7.0(3)I7(8)

Install All is the only option that supports upgrade and downgrade between releases. The following upgrade paths are supported:

■      Cisco NX-OS Release 6.0(2)A8(7b) and later > Cisco NX-OS Release 7.0(3)I7(8)

■      Cisco NX-OS Release 7.0(3)I7(3) and later > Cisco NX-OS Release 7.0(3)I7(8)

Upgrade Guidelines and Limitations

The following limitations are applicable when you upgrade from Releases 7.0(3)I7(2) or later to the NX-OS Release 7.0(3)I7(8):

■      If a custom CoPP policy is applied after upgrading to Cisco NX-OS Release 7.0(3)I7(2) or later, and if the Nexus 3548 switch is downgraded to Cisco NX-OS Release 5.0, where changes to the CoPP policy are not permitted, the custom CoPP policy is retained and cannot be modified.

■      copy r s and reload is not a supported method for an upgrade.

■      You must run the setup script after you upgrade to Cisco NX-OS Release 7.0(3)I7(8).

■      Cisco Nexus 3548 and 3548-X platform switches must run a “compact” NX-OS software image due to limited bootflash space. This “compact” image can be created using the NX-OS Compact Image procedure; alternatively, a compact NX-OS software image can be downloaded directly from Cisco's Software Download website. This requirement does not apply to the Cisco Nexus 3548-XL switch.

■      The MD5/SHA512 checksum published on Cisco's Software Download website for a compact NX-OS software image may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Compact Image procedure.

MIB Support

The Cisco Management Information Base (MIB) list includes Cisco proprietary MIBs and many other Internet Engineering Task Force (IETF) standard MIBs. These standard MIBs are defined in Requests for Comments (RFCs). To find specific MIB information, you must examine the Cisco proprietary MIB structure and related IETF-standard MIBs supported by the Cisco Nexus 3000 Series switch. The MIB Support List is available at the following FTP sites:

ftp://ftp.cisco.com/pub/mibs/supportlists/nexus3000/Nexus3000MIBSupportList.html

Unsupported Features

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

■      NetFlow

■      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

Supported Optics

To determine which transceivers and cables are supported by Cisco Nexus 3000 Series switches, see the Transceiver Module (TMG) Compatibility Matrix.

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.

Related Documentation

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

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

Documentation Feedback

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

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, 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

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.

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)

© 2021 Cisco Systems, Inc. All rights reserved.

[1] Cisco NX-OS Release 6.0(2)U6(3) is no longer available for a software download through www.cisco.com. This software release has been replaced by Cisco NX-OS Release 6.0(2)U6(3a).

[2] Cisco NX-OS Release 6.0(2)U6(2) is no longer available for a software download through www.cisco.com. This software release has been replaced by Cisco NX-OS Release 6.0(2)U6(2a).