Cisco Nexus 7000 Series NX-OS Release Notes, Release 6.2

---

Table 1 Online History Change

Date	Description
August 22, 2013	Created release notes for Release 6.2(2).
August 26, 2013	Added CSCuh18007to the “Open Caveats—Cisco NX-OS Release 6.2” section. Added the “ECMP Support in Hardware” limitation. Added the “CLI Command for Breakout Capabilities” limitation. Added a caveat about FEX queuing to the “Upgrade or Downgrade Caveats” section. Added IPv6 Inter-AS Option B lite as a supported MPLS feature.
September 5, 2013	Added CSCug37851 to the “Resolved Caveats—Cisco NX-OS Release 6.2(2)” section. Added CSCui13170 to the “Open Caveats—Cisco NX-OS Release 6.2” section. Updated the supported FEX modules for the N77-F248XP-23E I/O module in Table 3 . Added vPC and vPC+ to the “New Software Features” section. Updated OTV in the “New Software Features” section.
September 6, 2013	Updated the “ISSU Upgrade Steps” section. Updated “VACL Configuration Should Be Removed Before ISSU” in the “Upgrade or Downgrade Caveats” section. Added CSCtf36357 to the “Resolved Caveats—Cisco NX-OS Release 6.2(2)” section. Added Security Features to the “New Software Features” section.
September 10, 2013	Modified the description of the “Behavior of Control Plane Packets on an F2e Series Module” limitation. Added the “WCCP Support in a Mixed Mode VDC” limitation.
September 16, 2013	Updated vPC and vPC+ in the “New Software Features” section.
September 18, 2013	Added “Upgrade With an M2 Series Module Installed” to the “Upgrade/Downgrade Paths and Caveats” section.
September 30, 2013	Updated FabricPath in the “New Software Features” section.
October 16, 2013	Created release notes for Release 6.2(2a).
October 21, 2013	Added the Cisco Nexus B22 Fabric Extender for HP (N2K-B22HP) to Table 2 and Table 3 .
October 22, 2013	Updated the “Security Features” section of the “Cisco NX-OS Release 6.2(2) Software Features” section.
October 30, 2013	Updated Table 3 to add support for Cisco Nexus B22 Fabric Extender for HP (N2K-B22HP) on the 48-port 1/10 Gigabit Ethernet SFP+ I/O F2 Series module (N7K-F248XP-25).
November 21, 2013	Updated the “Limitations” section to add “Behavior of Control Plane Packets on an F2e Series Module”.
December 4, 2013	Updated Table 4 to list correct Product ID for the Cisco Nexus 7000 Series Network Analysis Module. Updated the “Open Caveats—Cisco NX-OS Release 6.2” section to add CSCul81224.
December 10, 2013	Updated Table 9 to add support for Fe and F2e Series modules hardware as ERSPAN destinations.
December 20, 2013	Created the release notes for Release 6.2(6).
January 6, 2014	Updated Table 3 to add FEX module support for the F3 Series modules in Release 6.2(6). Updated Table 5 to add the F3 Series modules and supported transceivers for Release 6.2(6)
January 7, 2014	Added Physical Port vPC to the new features for Release 6.2(6).
January 7. 2014	Updated the “OTV Support”section and the “OTV” section under New Software Features for Release 6.2(6).
January 8, 2014	Added the Cisco Nexus B22HP Fabric Extender for HP (N2K-B22HP) to the “Cisco Nexus Fabric Extenders” section.
January 4, 2014	Updated the ISSU and ISSD information in the “Upgrade/Downgrade Paths and Caveats” section.
January 22, 2014	Updated the “Open Caveats—Cisco NX-OS Release 6.2” section to add CSCul91443.
January 23, 2014	Updated the “Interoperability Between Modules” information.
January 24, 2014	Updated the Updated the “Limitations” section to add “The no hardware ejector enable Command is Not Recommended for Long-Term Use”
February 5, 2014	Updated the Cisco NX-OS Release 6.2(6) Software Features section to remove inaccurate FIPs certification feature from. Updated Table 3 to add the F3-Series 12-port 40-Gigabit Ethernet SFP+ I/O module (N7K-F312FQ-25) for Cisco Nexus 7000 switches.
February 17, 2014	Updated the “Features Available on F2, F2e, and F3 Series Modules” section to add MACSec support for the F2e Series modules. Updated “Interoperability Between Modules” section to add that you cannot interoperate the F3 Series plus the F2 and/or F2e Series plus M2 Series in the same VDC.
February 20, 2014	Updated “Non-ISSU Upgrade Steps” section.
February 26, 2014	Created the release notes for Release 6.2(6a).
March 10, 2014	Revised Table 5.
April 2, 2014	Removed support for ERSPAN destination for F3 Series modules.
April 3, 2014	Revised Tables 2 and 3.
April 8, 2014	Correct Cisco NX-OS Release to 6.2(6) for CLI command for breakout capabilities.
April 25, 2014	Created the release notes for Release 6.2(8).
April 26, 2014	Added two additional caveats to the “Open Caveats—Cisco NX-OS Release 6.2” section.
April 28, 2014	Added additional caveats to the “Caveats” section.
May 1, 2014	Added additional caveats to the “Caveats” section.
May 6, 2014	Added additional caveat to the “Open Caveats—Cisco NX-OS Release 6.2”section.
May 12, 2014	Updated information for LISP in “Cisco NX-OS Release 6.2(8) Software Features” section.
May 13, 2014	Added list of modules and required level of software to “CLI Command for Breakout Capabilities” section.
May 22, 2014	Added additional caveat to the “Caveats” section.
June 3, 2014	Updated Table 9 .
June 10, 2014	Updated Table 5 .
June 12, 2014	Added additional caveat to the “Caveats” section.
June 25, 2014	Added the “Resolved Caveats—Cisco NX-OS Release 6.2(8a)” section.
July 7, 2014	Added the “Resolved Caveats—Cisco NX-OS Release 6.2(6b)” section. Updated the “Supported Upgrade and Downgrade Paths” to add Release 6.2(6b) and Release 6.2(8a).
July 25, 2014	Updated the “Supported Upgrade and Downgrade Paths” tables to add 6.1(4a). Updated the “VDC Ports Can Become Unallocated After a Downgrade” caveat in the “Upgrade or Downgrade Caveats” section. Added an additional caveat to the“Upgrade or Downgrade Caveats” section. Added CSCup65230 to the “Resolved Caveats—Cisco NX-OS Release 6.2(2)”section.
August 8, 2014	Added an additional caveat to the“Upgrade or Downgrade Caveats” section. Updated the “Limitations” section to add “Native VLAN Change Causes Link Flap”. Added CSCug71801 to the “Resolved Caveats—Cisco NX-OS Release 6.2(2)”section.
September 11, 2014	Added CSCui72592 and CSCuo93631 to the “Open Caveats—Cisco NX-OS Release 6.2” section.
October 20, 2014	Created the release notes for Release 6.2(10).
November 5, 2014	Added CSCul05775 to “Open Caveats—Cisco NX-OS Release 6.2” section.
November 11, 2014	Added “Resolved Caveats—Cisco NX-OS Release 6.2(8b)” section.
November 14, 2014	Added CSCur57579 to “Open Caveats—Cisco NX-OS Release 6.2” section.
November 17, 2014	Updated the “Cisco NX-OS Release 6.2(10) Software Features” section to add “License Requirement MP-BGP RR for FabricPath (aka DFA).”
February 3, 2015	Created the release notes for Release 6.2(12).
February 4, 2015	Added CSCus76724 to “Open Caveats—Cisco NX-OS Release 6.2”section.
February 12, 2015	Updates to “Open Caveats—Cisco NX-OS Release 6.2” and “Resolved Caveats—Cisco NX-OS Release 6.2(12)” sections. Updated the “Supported Upgrade and Downgrade Paths”.
March 2, 2015	Removed “Not Customer Visible” Bugs from the “Caveats” section.
April 23, 2015	Added CSCub54436 to the “Resolved Caveats—Cisco NX-OS Release 6.2(2)”section.
May 20, 2015	Added CSCuq39448 to the “Open Caveats—Cisco NX-OS Release 6.2”section.
May 25, 2015	Added CSCuo82450 to the “Resolved Caveats—Cisco NX-OS Release 6.2(12)” sections.

Memory Requirements

Cisco NX-OS Release 6.2 software requires 8 GB of memory. If you have a Cisco Nexus 7000 Series system with a Supervisor 1 module with 4 GB of memory, you must upgrade to 8 GB of memory using the memory upgrade kit, N7K-SUP1-8GBUPG=, before you install Cisco NX-OS Release 6.2.

Instructions for upgrading to the new memory are available in the “Upgrading Memory for Supervisor Modules” section of the Cisco Nexus 7000 Series Hardware Installation and Reference Guide.

Supported Device Hardware

The Cisco NX-OS software supports the Cisco Nexus 7000 Series that includes Cisco Nexus 7000 switches and Cisco Nexus 7700 switches. You can find detailed information about supported hardware in the Cisco Nexus 7000 Series Hardware Installation and Reference Guide .

Table 2 shows the Cisco Nexus 7000 Series hardware supported by Cisco NX-OS Release 6.x, Release 5.x, and Release 4.x software.

Table 3 shows the FEX modules supported by the Cisco Nexus 7000 Series I/O modules.

Table 4 shows the service modules supported by the Cisco Nexus 7000 Series switches.

Table 5 shows the transceiver devices supported by each release.

For a list of minimum recommended Cisco NX-OS software releases for use with Cisco Nexus 7000 Series switches, see the document Minimum Recommended Cisco NX-OS Releases for Cisco Nexus 7000 Series Switches.

1.Requires the Cisco Nexus 7010 Scalable Feature Package license (N7K-C7010-XL) or the Cisco Nexus 7018 Scalable Feature Package license (N7K-C7018-XL), depending on the chassis, to enable all XL-capable I/O modules to operate in XL mode.

2.FEX server-facing interfaces should be configured in autonegotiate mode. Do not force a specific data rate. See DDTS CSCuj84520 for additional information.

---

Note The Cisco Nexus 7000 Enhanced F2 Series 48-port 1/10 GBASE-T RJ-45 Module (N7K-F248XT-25E) does not support Cisco Nexus 2000 Fabric Extenders.

 

3.For a complete list of supported optical transceivers of this type, go to the Cisco Transceiver Module Compatibility Information page. 4.Multimode fiber supported on ports 41 to 48 only. Single-mode fiber support if applicable to all ports. 5.Minimum version supported is -02. 6.Requires CVR-X2-SFP10G, OneX Converter Module (X2 to SFP+ Adapter)

---

Supported Upgrade and Downgrade Paths

---

Note Before you upgrade or downgrade your Cisco NX-OS software, we recommend that you read the complete list of caveats in this section to understand how an upgrade or downgrade might affect your network, depending on the features that you have configured.

Do not change any configuration settings or network settings during a software upgrade. Any changes in the network settings might cause a disruptive upgrade.

See Table 6 for the in-service software upgrade (ISSU) path to Cisco NX-OS Release 6.2(x). Releases that are not listed for a particular release train do not support a direct ISSU or ISSD to the current release.

---

Note Only the ISSU combinations in the following table have been tested and are supported.

 

See Table 7 for the in-service software upgrade (ISSU) path to Cisco NX-OS Release 6.2(x) for the Cisco Nexus 7700 Series chassis. Releases that are not listed for a particular release train do not support a direct ISSU or ISSD to the current release.

Unless otherwise noted, all releases within the same release train are ISSU and ISSD compatible to releases within the same train.

If you are running a Cisco NX-OS release earlier than Release 5.2, you can perform an ISSU in multiple steps. Table 8 lists the supported multistep ISSU paths.

ISSU Upgrade Steps

To perform an ISSU upgrade to Release 6.2(x) from one of the ISSU supported releases listed in Table 6 , follow these steps:

1. Enter the show running-config aclmgr inactive-if-config command for all VDCs.

2. Enter the clear inactive-config acl command for all VDCs.

3. If the configuration has any mac packet-classify configurations on any interfaces, remove all of the configurations by entering the no mac packet-classify command.

4. If there is an VACL configuration and the ISSU to Release 6.2(2a) is from a release earlier than Release 6.1(3), perform the ISSU in two steps:

a. Upgrade to Release 6.1(3) or Release 6.1(4).

b. Upgrade from Release 6.1(3) or Release 6.1(4) to Release 6.2(2a).

5. Start the ISSU procedure.

Non-ISSU Upgrade Steps

To perform a non-ISSU upgrade to Release 6.2(x) from any release earlier than Release 6.2(x), follow these steps:

1. Change the boot variable.

2. Enter the copy running-config startup-config vdc-all command.

3. Enter the reload command to reload the switch.

---

Note Allow time after the reload for the configuration to be applied.

To perform a non-ISSU upgrade from any PRIOR supported Cisco NX-OS release to Release 6.2(2) or 6.2(2a), follow these steps:

1. Enter the show running-config aclmgr inactive-if-config command for all VDCs.

2. Enter the clear inactive-config acl command for all VDCs.

3. Change the boot variable to boot Release 6.2(2) or 6.2(2a).

4. Enter the copy running-config startup-config vdc-all command.

5. Enter the reload command to reload the switch.

---

Note Allow time after the reload for the configuration to be applied.

6. Once all line cards come up, enter the show running-config aclmgr command in all VDCs.

7. Enter the clear inactive-config acl command for all VDCs.

8. Enter the copy boot flash:/vdc_x/aclmgr-inactive-config.cfg running-config command for all VDCs.

For complete instructions on upgrading your software, see the Cisco Nexus 7000 Series NX-OS Upgrade Downgrade Guide.

Non-ISSU upgrades are also referred to as a cold boot.

Upgrade or Downgrade Caveats

A software upgrade or downgrade can be impacted by the following features or hardware:

• The online diagnostics tests PortLoopbackTest, SnakeLoopbackTest, RewriteEngineText, and BootupPortLoopbackTest are not supported on the N77-F348XP-23 module.
• Feature Support

Any features introduced in a release must be disabled before downgrading to a release that does not support those features.

• Unsupported Modules

When manually downgrading from Cisco NX-OS Release 6.2(2) to an earlier release, first power down all modules that are unsupported in the downgrade image. Then, purge the configuration of the unsupported modules using the purge module module_number running-config command.

• The Intelligent Traffic Director (ITD) Configuration is Lost After an Upgrade or Downgrade

The ITD configuration is not saved during an in-service software upgrade (ISSU) from Release 6.2(8) or Release 6.2(8a) to Release 6.2(10) or an in-service software downgrade (ISSD) to Release 6.2(8a) or Release 6.2(8). Before performing an ISSU or ISSD, you must remove the ITD configuration by using the no feature itd command. After the upgrade or downgrade, you must manually reapply the configuration.

• OTV AED Displays a Version Mismatch After an Upgrade

If your OTV setup includes dual Authoritative Edge Devices (AEDs), the output of the show otv command displays a Version Mismatch after you perform an upgrade to from Release 6.1.X to Release 6.2.x because one AED is upgraded to 6.2.x and second AED is still running Release 6.1.x or an earlier release. This behavior is expected. For example:

• The Auto-Recovery Disable and Auto-Recovery Timeout Configurations Might not be Persistent Across an Upgrade, Downgrade, or Reload.

Before Cisco NX-OS 6.2(2), the auto-recovery default was disabled. In Cisco NX-OS Release 6.2(2) and later releases, auto recovery is enabled by default. Because the default behavior of auto recovery is changed, the following caveats apply:

– After you perform an ISSU to Release 6.2(2) or a later release, auto recovery is enabled by default after the upgrade. If you want to disable auto recovery in Release 6.2(2) or a later release, you must use the no auto-recovery command to explicitly disable auto recovery.

– After you perform a downgrade from Release 6.2(6) or 6.2(4a) to Release 6.2(2), auto recovery is enabled by default after the downgrade regardless of the auto-recovery configuration before the downgrade. If you want to disable auto recovery in Release 6.2(2) or a later release, you must use the no auto-recovery command to explicitly disable auto recovery.

– After you reload a device that is running Release 6.2(2), 6.2(4a) or 6.2(6), auto recovery is enabled by default after the reload. If you want to disable auto recovery in Release 6.2(2) or a later release, you must use the no auto-recovery command to explicitly disable auto recovery after the reload.

– If you changed the auto-recovery reload-delay value from the default value in Release 6.2(2), 6.2(4a), or 6.2(6), the value reverts to the default (240sec) after you perform a downgrade to any of the three specified releases and after you reload a device that is running any of the three specified releases. If you want a value other than the default for the auto-recovery reload-delay, you must reconfigure the auto-recovery reload-delay value after the downgrade or the reload.

• Auto Recovery Does not Restore the vPC.

After a disruptive upgrade or sequential reloads, the Auto Recovery feature does not restore the vPC when the keep-alive and peer-link are down. By design, a disruptive upgrade causes the start-up configuration to run through a different process when it is installed. This issue is seen on sequential reloads until the binary configuration is rebuilt.

To ensure that auto recovery is successful and the vPC is restored after a disruptive upgrade, use the save running-config startup-config vdc-all command after the disruptive upgrade and then reload the device.

• Supervisor CoS2q and DSCP2Q Mappings are Restored to Default Mappings

After you perform an ISSU to Cisco NX-OS Release 6.2(6a) or a later release, one of the following warning messages is displayed:

– Supervisor cos2q, dscp2q mappings are restored to default mappings. Please apply cos2q, dscp2q mappings again. For dscp2q mappings, turn off and on dscp global knob.

– Supervisor cos2q mappings are restored to default mappings. Please apply cos2q mappings again.

– Supervisor dscp2q mappings are restored to default mappings. Please turn off and on dscp global knob.

If you are using the 8e4q4q template in Cisco NX-OS Release 6.2(6) or an earlier release and you perform an ISSU to Release 6.2(6a) or a later release, the Class of Service (Cos2q) and differentiated services code point (DSCP2q) maps are restored to the defaults in the supervisor engine. However, because the ISSU is non-disruptive, the mappings are not programmed in the hardware. The next time you save a new configuration, the default mappings are pushed to the module, which is disruptive.

To avoid this issue, you must explicitly push the COS2q and DSCP2q mappings to the module after the ISSU.

If you are not using the 8e4q4q template and you perform an ISSU from Cisco NX-OS Release 6.2(6) or an earlier release to Release 6.2(6a) or a later release, you can ignore the warning message; no action is required.

• VDC Ports Can Become Unallocated After a Downgrade

If your Cisco Nexus 7000 Series device that is running Release 6.2(x) has f2e in its configuration as a part of the limit-resource module-type command, some interfaces might become unallocated after a downgrade from Release 6.2(x) to Release 6.1(x) or an earlier release.

Because there is no f2e keyword for the limit-resource module-type f2 f2e command in releases before Release 6.2(x), the command fails and the VDC is converted to a limit-resource module-type m1 f1 m1xl m2xl VDC. This issue can occur even if you do not have any F2e Series modules in the chassis.

To avoid this issue, do one of the following procedures:

---

Note Before any upgrade, save the startup configuration to bootflash.

– If you have a saved backup of the switch configuration from the release to which you want to downgrade, do the following:

1. Before downgrading to Release 6.1(x) or an earlier release, change the boot variable to 6.1(x).

2. Enter the copy running-config startup-config command to save the boot variable to 6.1(x).

3. Enter the write erase command on the switch.

4. Reload the switch with the downgrade image.

5. After all I/O modules and supervisor modules come up, enter the copy saved-config running-config command. For example, if your saved configuration is in the file bootflash:saved_config, enter the copy bootflash:saved_config running-config command.

– If you do not have a backup switch configuration from the release to which you want to downgrade, follow these steps to change instances of f2e to f2 in the limit-resource module-type command of the Release 6.2(x) configuration, before reloading the switch:

1. Copy your release 6.2(x) configuration to a file on a remote server by entering the copy running-config scp:// command.

2. In the copied file, find all instances of f2e in the limit-resource module-type f2 f2e command and replace it with f2. Remove any redundant instances of f2. For example, if you replace f2e in the limit-resource module-type f2 f2e command, make sure that you change it to limit-resource module-type f2. Save the file.

3. Enter the copy running-config startup-config command to save the boot variable to 6.2(x).

4. Enter the write erase command on the switch.

5. Reload the switch with the downgrade image.

6. After all I/O modules and supervisor modules come up, copy the edited file to your running configuration by entering the copy saved-config running-config command.

• F2e Interfaces Might Become Unallocated After an Upgrade

All F2e interfaces might become unallocated immediately after an upgrade from Cisco NX-OS Release 6.1(x) to Release 6.2(x). Generally, this situation should not occur if you follow recommended upgrade procedures. However, if you find that all F2e interfaces are unallocated after the upgrade, before doing any further configuration, complete the following steps to fix the problem:

1. Retrieve an ASCII version of the complete switch configuration and edit it as follows:

– Replace every instance of f2 with f2 f2e in any limit-resource module-type command and any system module-type command.

2. When all the modules are online and all the VDCs are created and in active status, in the context of the Default VDC or the Admin VDC, enter the copy modified-ascii-config running-config echo command to apply the modified ASCII configuration file.

3. After verifying the sanity of the current configuration in the context of the Default VDC or the Admin VDC, enter the copy running-config startup-config vdc-all command to save the configuration.

• Storage VDC

Starting with Cisco NX-OS Release 6.2(x), shared interfaces must come from the module types that the storage VDC supports, and having F1 and F2 interfaces shared in the same VDC is not supported. In Release 6.2(x), the vdc command will fail if you attempt to share F2 interfaces with a VDC that supports only F1 (or vice versa).

In Cisco NX-OS Release 6.1(x), you are allowed to share F2 interfaces with a storage VDC that supports only F1, and you can share F1 interfaces with a storage VDC that supports only F2. But having F1 and F2 shared interfaces in the same storage VDC is somewhat problematic and can potentially cause issues.

If you have a Cisco NX-OS Release 6.1(x) configuration that has shared F1 and F2 interfaces in the same storage VDC, this configuration will be allowed temporarily in Release 6.2(x) if you are performing an upgrade through a binary configuration, which is the typical upgrade path, rather than through an ASCII configuration. This temporary situation provides a transition period to update the configuration; however, the functionality of the interfaces is not guaranteed during this time. The configuration might be lost after a switch reboot. In addition, the configuration will fail in Release 6.2(x), if you remove the interface and attempt to add it back to a shared storage VDC. Because of these constraints, we recommend that you remove the combination of shared interfaces before the upgrade to Release 6.2(x), or after it.

Before or after an upgrade from Cisco NX-OS Release 6.1(x) to Release 6.2(x), apply either the limit-resource module-type f1 command or the limit-resource module-type f2 command to the storage VDC, and check that the following storage VDC configurations are removed:

– Shared F2 interfaces with a storage VDC that support only F1, or shared F1 interfaces with a storage VDC that supports only F2

– F1 and F2 interfaces in the same storage VDC

• Upgrade With an M2 Series Module Installed

In rare instances, if you perform an ISSU from Cisco NX-OS Release 6.1(2) or an earlier release to Release 6.2(x) and you have an M2 or F2 Series module installed in your Cisco Nexus 7000 Series system, the upgrade might fail with the following error:

To work around this issue, ISSU to Release 6.1(3) before you upgrade to Release 6.2(x) or a later release, or upgrade via a traditional reload. For additional details, see CSCud63092.

• FEX Host Interface

When you upgrade Cisco NX-OS software by changing boot variables and reloading the device, make sure to save the FEX HIF configuration to the startup configuration, as well as another location (such as bootflash or an external server). Once the upgrade to a new release is complete, and the FEX is fully online and associated, reapply the FEX HIF configuration.

---

Note During the process of Cisco Fabric Extender (FEX) modules getting connected to a Cisco Nexus 7000 Series switch, if the switch is manually upgraded or downgraded, FEX host interfaces (HIFs) lose the configuration. To avoid it, if you are manually upgrading the vPC system, you must save the FEX HIF (FEX host interfaces connected to hosts) configurations to both the startup configuration file and to an external device before starting the reload, and reapply the configuration once the FEX module is fully online.

• FEX Queuing

The FEX queuing feature is enabled by default if you perform an ISSU to a release that supports this feature from an earlier release that supports this feature. The feature is not enabled if you perform an ISSU to a release that supports this feature from an earlier release that does not support this feature.

For an ISSU to Cisco NX-OS Release 6.2(2a) from Release 6.1(x), you must reload the FEX to enable FEX queuing after the ISSU. Enter the show queuing interface fex-hif-port command to verify if FEX queuing is enabled on a given FEX.

• VACL Configuration Should Be Removed Before ISSU

If an active or inactive VACL configuration is present in the running configuration, an ISSU from any release earlier than Cisco NX-OS Release 6.1(3) to Release 6.2(2a) will not succeed.

Enter the show running-config aclmgr inactive-if-config command to check for inactive policies. You can remove these policies by entering the clear inactive config acl/qos command.

To work around this issue, remove all VACLs from the system before the ISSU, or perform a two-step upgrade to Release 6.1(3) and then to Release 6.2(2a).

• The MAC Packet Classify Configuration Should Be Removed Before ISSU

If the mac packet-classify command is configured for any interface, the ACLMGR process might fail during an ISSU to Cisco NX-OS Release 6.2(2a).

To work around this issue, remove all mac packet-classify commands from the configuration for all interfaces before the ISSU.

• OTV

Any upgrade from an image that is earlier than Cisco NX-OS Release 6.2(2) to an image that is Cisco NX-OS Release 6.2(2) or later in an OTV network is disruptive. When you upgrade from any previous release, the OTV overlay needs to be shut down for ISSU to operate.

For more details, see the “Preparing OTV for ISSU to Cisco NX-OS 5.2(1) or Later Releases in a Dual-Homed Site” section in the Cisco Nexus 7000 Series NX-OS OTV Configuration Guide.

• LISP

If you have LISP configured on a Cisco Nexus 7000 Series device, you must remove the configuration before an ISSU.

• OSPF

Cisco NX-OS Release 6.1 supports an increased number of Open Shortest Path First (OSPF) process instances per VDC. See the Cisco Nexus 7000 Series NX-OS Verified Scalability Guide for the latest verified number.

If you have more than four OSPF v2 or more than four OSPF v3 process instances configured and you manually downgrade to an earlier release, you must remove instances 5 and higher. Use the following command to match an OSPF v2 process tag with an OSPF process instance:

Use the show system internal sysmgr service name ospfv3 command to match an OSPF v3 process tag with an OSPF v3 process instance.

This enhancement was added for EIGRP and ISIS with Cisco NX-OS Release 6.2.

• ACL

During an ISSU from Cisco NX-OS Release 5.2(x) or Release 6.1(x) to Release 6.2(2a), the system prompts you to clear inactive access control list (ACL) configurations. Enter the clear inactive-config acl command to clear any inactive ACL configurations.

• CoPP

The default Control Plane Policing (CoPP) policy does not change when you upgrade the Cisco NX-OS software.

If you manually downgrade without using ISSD to a release earlier than NX-OS Release 5.2(1), the CoPP configuration is lost, and a CoPP policy is no longer attached to the control plane.

• Aggressive Failure Detection Timers

ISSU, stateful switchover (SSO), and graceful restart are not supported when aggressive failure detection timers are used for any Layer 3 protocols. Starting in Cisco NX-OS Release 5.2(3a), the First Hop Redundancy Protocol (FHRP) with aggressive timers has been validated for SSO or ISSU using the extended hold timer feature. Other protocols such as OSPF have been validated with aggressive timers without SSO or ISSU support. For additional information on aggressive timer support and extended hold timers for FHRP, see the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide.

• IPFIB Errors

During an upgrade to Cisco NX-OS Release 5.2(7) or a later release, the following error messages might appear:

In addition, the ipfib process might fail.

This issue can be triggered when the following sequence of events occur:

– You perform an ISSU to Cisco NX-OS Release 5.2(1), Release 5.2(3a), Release 5.2(4), or Release 5.2(5) release from an earlier 5.0(x) or 5.1(x) release and you have not reloaded the switch.

– You make configuration changes in the 5.2(x) release running on the Cisco Nexus 7000 Series system.

– You perform an ISSU to NX-OS Release 5.2(7) or a later release.

To work around this issue, follow these steps:

1. Prior to the upgrade, enter the following commands to avoid the issue:

a. Enter the feature lisp command.

b. Enter the ip lisp etr command for all virtual routing and forwarding (VRF) instances, followed by the no ip lisp etr command.

c. Enter the no feature lisp command.

2. If you experience this issue, reload the affected modules on your Cisco Nexus 7000 Series system.

---

Note The Transport Services Package license is required to enable the Locator/ID Separation Protocol (LISP). If you do not have this license, you can enable the grace period for it. If you cannot enable the grace period, perform an ISSU and reload the affected modules.

Perform these steps even if you are not using LISP because the issue can occur even if LISP is not running.

• BGP

If both send-community and send-community extended are in the configuration for Cisco NX-OS 6.1 or an earlier release and an ISSU is performed, only send-community extended will be present in the configuration for a Cisco NX-OS 6.2 or later release after the ISSU. You will have to manually reconfigure send-community. The running configuration will show send-community both instead of both commands.

New Hardware in Cisco NX-OS Release 6.2(12)

Cisco NX-OS Release 6.2(12) introduces new hardware:

• N7K-F348XP-25

The Cisco Nexus 7000 F3-Series module is a low-latency, high-performance, high-density 1/10 Gigabit Ethernet module. It is operationally consistent with the Cisco Nexus 7700 F3-Series modules and shares a common system architecture and the same application-specific integrated circuit (ASIC) technology.

New Hardware in Cisco NX-OS Release 6.2(10)

Cisco NX-OS Release 6.2(10) introduces new hardware:

• N7K-F306CK-25

Cisco NX-OS 6.2(10) supports the Cisco Nexus 7000 F3-Series 6-Port 100 Gigabit Ethernet Module. The Cisco Nexus 7000 F3-Series module is a low-latency, high-performance, high-density 100 Gigabit Ethernet module. It is operationally consistent with the Cisco Nexus 7700 F3-Series modules and shares a common system architecture and the same application-specific integrated circuit (ASIC) technology.

New Hardware in Cisco NX-OS Release 6.2(8)

Diagnostic Optical Monitoring (DOM) is supported on the F3 Series modules in Cisco NX-OS Release 6.2(8).

Breakout cables and 40-Gigabit copper cables are available for the following modules:

• N77-F324FQ-25
• N7K-F312FQ-25
• N7K-M206FQ-23L

The Cisco Nexus 2248TP-E FEX supports 10 Mbps. transmission speeds.

New Hardware in Cisco NX-OS Release 6.2(6)

Cisco NX-OS Release 6.2(6) introduces new hardware that is described in the following sections:

• Cisco Nexus 7706 Switch
• Cisco Nexus 7000 Series I/O Module
• Cisco Nexus 7700 Series I/O Modules

See Table 2 for the PIDs associated with the hardware components described in this section.

In addition, Release 6.2(6) introduces new cables that allow you to expand the number of ports on selected modules. These cables allow you to connect to one of the 40-Gigabit Ethernet ports on the following modules and connect the other end to up to four 10-Gigabit Ethernet ports. Two cables are available and offer the following:

• Support for the Cisco Nexus 7000 F3 Series 12-port 40-Gigabit Ethernet (QSFP+) Module to support up to 48 10-Gigabit Ethernet ports per slot for 18-slot, 10-slot, 9-slot, and 4-slot chassis.
• Support for the Cisco Nexus 7000 M2-Series 6-port 40-Gigabit Ethernet I/O Module XL to support up to 24 10-Gigabit Ethernet ports per slot for 18-slot, 10-slot, 9-slot, and 4-slot chassis.

Cisco Nexus 7706 Switch

The Cisco Nexus 7706 switch is a 6-slot chassis that delivers 1.32 Gbps per slot. It has two half-width slots for Supervisor 2E modules and four full-width slots for I/O modules. With the F3 Series modules, the switch provides 40-Gigabit Ethernet and 100-Gigabit Ethernet ports. The supervisor modules and I/O modules are interchangeable between the Cisco Nexus 7710 switch and the Cisco Nexus 7706 switch.The switch supports up to six fabric modules and uses three fan tray that provide front-to-back airflow cooling. To power the switch, you can use one or two AC or DC 3-kW power supply units, and you can use up to two more power supplies to provide power-supply or grid power redundancy.

Cisco Nexus 7000 Series I/O Module

Cisco NX-OS Release 6.2(6) supports the Cisco Nexus 7000 F3 Series 12-port 40-Gigabit Ethernet (QSFP+) Module (F3 Series).

This multiprotocol module supports Ethernet, FabricPath, FCoE, OTV, LISP, and VXLAN, MPLS, VPLS, DFA. This module supports Cisco Nexus 2000 Series Fabric Extenders.

Cisco NX-OS Release 6.2(8) supports F3 line cards as first hop in a LISP multi-hop setup.

Cisco Nexus 7700 Series I/O Modules

Cisco NX-OS Release 6.2(6) supports the following modules for the Cisco Nexus 7700 Series switch:

• Cisco Nexus 7700 F3 Series 48-port 1/10-Gigabit Ethernet (SFP+) Module (F3 Series)
• Cisco Nexus 7700 F3 Series 24-port 40-Gigabit Ethernet (SFP+) Module (F3 Series)
• Cisco Nexus 7700 F3 Series 12-port 100-Gigabit Ethernet (SFP+) Module (F3 Series)

These multiprotocol modules support Ethernet, FabricPath, FCoE, OTV, LISP, VXLAN, MPLS, VPLS, and DFA. These modules, except the 12-port 100-Gigabit Ethernet module, support Cisco Nexus 2000 Series Fabric Extenders.

Cisco NX-OS Release 6.2(8) supports F3 line cards as first hop in a LISP multi-hop setup.

New Hardware in Cisco NX-OS Release 6.2(2)

Cisco NX-OS Release 6.2 introduces new hardware that is described in the following sections:

• Cisco Nexus 7710 Switch
• Cisco Nexus 7718 Switch
• Cisco Nexus 7700 Series I/O Module
• Cisco Nexus Fabric Extenders
• Cisco Nexus 7000 Series Network Analysis Module

See Table 2 for the PIDs associated with the hardware components described in this section.

Cisco Nexus 7710 Switch

The Cisco Nexus 7710 switch is a 10-slot chassis that delivers 1.32 Gbps per slot. It has two half-width slots for two Supervisor 2E modules and eight full-width slots for I/O modules. The switch supports up to six fabric modules and up to eight 3000 W power supply units. There are three fan trays. Airflow is front to back in the Cisco Nexus 7710 switch.

Cisco Nexus 7718 Switch

The Cisco Nexus 7718 switch is a 18-slot chassis that delivers 1.32 Gbps per slot. It has two half-width slots for two Supervisor 2E modules, and 16 full-width slots for I/O modules. The switch supports up to 6 fabric modules and up to 16 3000 W power supply units. There are three fan trays. Airflow is front to back in the Cisco Nexus 7718 switch.

Cisco Nexus 7700 Series I/O Module

Cisco NX-OS Release 6.2(2) supports the Cisco Nexus 7700 Enhanced F2-Series 48-port 1/10-Gigabit Ethernet (SFP+) Module (F2e Series).

This multiprotocol module supports Ethernet, FabricPath, and FCoE, and it supports Cisco Nexus 2000 Series Fabric Extenders.

Cisco Nexus Fabric Extenders

Cisco NX-OS Release 6.2(2) supports the following Cisco Nexus Fabric Extenders:

• Cisco Nexus 2232TM-E 10GE Fabric Extender
• Cisco Nexus 2248PQ-10GE Fabric Extender

For additional information, see the Cisco Nexus 2000 Series Hardware Installation Guide.

• Cisco Nexus B22HP Fabric Extender (blade fabric extender for HP)

For additional information, see the Cisco Nexus B22 Fabric Extender for HP Getting Started Guide.

Cisco Nexus 7000 Series Network Analysis Module

The Cisco Nexus 7000 Series Network Analysis Module (Cisco NAM-NX1) is the first service module for the Cisco Nexus 7000 Series platform. With the Cisco NAM-NX1, you can implement network analysis and monitoring in the data center. Cisco NAM-NX1 can be installed into any one of the network module slots on a Cisco Nexus 7000 Series switch.

For additional information, see the Cisco Prime Network Analysis Module User Guide 6.0.

New Hardware in Cisco NX-OS Release 6.2(2a)

Cisco NX-OS Release 6.2(2a) does not include new hardware.

VDC Changes in Cisco NX-OS Release 6.2

Cisco NX-OS Release 6.2(2) provides several changes to VDCs that apply to Cisco Nexus 7000 Series switches and Cisco Nexus 7700 Series switches.

• For a chassis with only F2e Series modules, the default VDC will be created using an F2e Series module as a supported module, unless you apply your own configuration.
• In Release 6.2(2), F2 Series modules can only be a part of an F2 VDC or an F2-F2E VDC.
• The F2e and F2 Series modules cannot exist with the F1 Series module in a VDC.
• A new VDC type, F2E, supports only F2e Series modules, but can be added to other VDC types to allow F2E to be part of the same VDC with F2 modules, or M1 or M2 Series modules. An F2e Series module and any M Series module can be configured in the same VDC.
• During an upgrade to Cisco NX-OS Release 6.2(2), if you have F2 and F2e Series modules, the VDC type automatically changes to the F2-F2E VDC.
• In an F2-F2E VDC, only the features supported on the F2 Series module are supported.

Review the “Upgrade or Downgrade Caveats” section for information related to VDCs that you should be aware of before upgrading to Cisco NX-OS Release 6.2(2).

For additional information, see the Cisco Nexus 7000 Series NX-OS VDC Configuration Guide.

Features Available on F2, F2e, and F3 Series Modules

Some software features are not available on the F2 or F3 Series modules in Cisco NX-OS Release 6.x. See Table 9 for a list of features that have hardware and software support on the F2, F2e, and F3 Series modules.

Table 9 Feature Support on F2 Series, F2e Series, and F3 Series Modules

 

---

Note The same features that are supported on an F2 Series module on a Cisco Nexus 7000 Series switch are also supported on a Cisco Nexus 7700 Series switch.

---

Note On the F3 Series, only the 10-Gigabit I/O module offers MACSec capabilities. The 40-Gigabit and 100-Gigabit F3 Series modules do not support MACSec.

Cisco NX-OS Release 6.2(2) Software Features

Cisco NX-OS Release 6.2(2) includes the new features described in the following sections:

• MPLS
• FabricPath
• VDC
• vPC and vPC+
• OTV
• Routing Capabilities
• Security Features
• SPAN
• LISP
• IPSLA
• FEX
• ISIS MT
• Confirm Commit Device Alias

MPLS

New MPLS features in Release 6.2(2) include the following:

• Any Transport over MPLS (AToM), which accommodates different types of Layer 2 packets, including Ethernet and VLAN, to enable the service provider to transport different types of traffic over the backbone.
• Pseudowire provisioning for AToM, which enables you to configure static pseudowires in cases where you cannot use directed control protocols, such as the Label Distribution Protocol or Resource Reservation Protocol over traffic-engineered tunnels (RSVP-TE).
• Ethernet over Multiprotocol Label Switching (EoMPLS), which is a Virtual Private Wire Service (VPWS) that is used to carry Layer 2 Ethernet frames over an MPLS network. EoMPLS enables service providers to offer emulated Ethernet services over existing MPLS networks.
• EoMPLS Graceful Restart, which adds support for a switch that is configured with the Label Distribution Protocol (LDP) Graceful Restart (GR) to assist its neighboring switches to recover gracefully from an interruption in service.
• Layer 2 and Layer 3 load balancing coexistence, which supports Layer 3 VPN and Layer 2 VPN forwarding that is performed independently on the switch using two different types of adjacencies. The forwarding is not impacted by having a different method of load balancing for the Layer 2 VPN.
• Virtual Private LAN Service, which supports a point-to-multipoint service between multiple customer sites using a mesh of point-to-point pseudowires over the provider core to emulate a LAN between the sites.
• Inter-AS Option B lite is supported.

FabricPath

FabricPath has been enhanced to include the following:

• Anycast Hot Standby Router Protocol (HSRP)
• An overload bit
• Support for multiple topologies (ISIS-MT)
• Layer 2 proxy learning
• Scale improvements

VDC

New VDC features in Release 6.2(2) are as follows:

• A new VDC type, F2e
• An Administrator VDC on the Supervisor 1 module
• Support for an F2e Series module and an M Series module in the same VDC

vPC and vPC+

Cisco NX-OS Release 6.2(2) includes the following new vPC and vPC+ features:

• A best practice macro for vPCs can be enabled in vPC domain configuration mode with the mode auto command. This feature enables the following vPC best practice features:

– peer gateway

– auto recovery

– ip arp synchronize

– ipv6 nd synchronize

• Release 6.2(2) supports Source-Specific Multicast (SSM) in a vPC+ domain.