HP Cisco MDS 9134 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) - Page 9

Limitations Send documentation comments to [email protected] interface vfc 1 no shutdown vsan database vsan 1 interface vfc 1 Upgrading to Cisco NX-OS Release 4.0(1a)N1(1) When you upgrade your Cisco Nexus 5000 Series switch to Cisco NX-OS Release 4.0(1a)N1(1) all virtual Fibre Channel and virtual Ethernet interface configuration will be lost because the applicable CLI is incompatible with the previous releases. We recommend that you backup your startup-config file prior to performing the upgrade. If your switch has an FCoE configuration you will need to reconfigure FCoE using the new FCoE CLI. Alternatively, you can contact Cisco Customer Support for help with upgrading and converting your configuration to the new format. Downgrading from Cisco NX-OS Release 4.0(1a)N1(1) Your FCoE configuration will be lost on downgrade. We recommend that you backup your original configuration prior to upgrading to Cisco NX-OS Release 4.0(1a)N1(1). The backed up startup-config can be used to restore your original configuration after a downgrade. Refer to the following section for details. Downgrade Steps for FCoE Configurations The following steps are required to restore your FCoE configuration after a downgrade from Cisco NX-OS Release 4.0(1a)N1(1): 1. Downgrade the switch to your pre-4.0(1a)N1(1) image using the install all command. 2. After the downgrade completes, clear the switch configuration using the write erase command followed by the reload command. 3. Reconfigure the switch by running the feature fcoe and copy running startup commands. For a switch running in NPV mode run the npv enable command. Reload the switch by running the reload command. 4. Restore your pre-upgrade configuration using the copy pre-4.0(1a)N1(1)-config running-config command. Limitations This section describes the limitations in Nexus 5000 Series switches, Release 4.0(1a)N1(1). General • The untagged cos command is not supported in this release. • Traffic going out the Ethernet SPAN destination is always tagged. The SPAN destination can be in the access or trunk mode and frames on the SPAN source port can be tagged or untagged. Frames are always tagged internally as they travel through the system. Information about whether the frame OL-16601-01 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) 9