HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes Release 4.0(1a)N1(1a - Page 5

Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues Send documentation comments to [email protected] • If the startup-config has an RBAC role configured with more than 35 rules, then after a downgrade to the 4.0(0)N1(2a) release, the show running-config command causes the vshd process to core dump. This is due to a caveat (CSCsy37432). The workaround is to remove rules from the roles configuration in a way that a role does not have more than 35 rules before downgrading to the 4.0(0)N1(2a) release. • If the startup-config has an RBAC role configured with more than 20 roles with 20 rules each, then after a downgrade to the 4.0(0)N1(2a) release, show running-config will make the roles feature work incorrectly. This is due to caveat CSCsy53275. The workaround is, before you downgrade to the 4.0(0)N1(2a) release, remove rules from the roles configuration to limit the configuration so it does not exceed the previously mentioned numbers. • After an upgrade or downgrade, if the show startup security command is issued before performing copy running-config startup-config, the security process could crash. This is due to caveat CSCsy09062. You can avoid a core dump by issuing a copy running-config startup-config command after an upgrade or downgrade and before issuing the show startup command. • After an upgrade or downgrade, when the system comes up users are assigned a default role of network-operator. This is due to caveat CSCsy08516. To avoid the problem, reload the switch after an upgrade or a downgrade and after the system comes up. You can then perform a copy running-config startup-config to save the correct configuration. For more information about the features listed, refer to the documentation set listed in the"Related Documentation" section on page 26. This section includes the following topics: • EtherChannel® Upgrade/Downgrade Changes, page 5 • Fibre Channel Port Shutdown, page 7 • Switched Port Analyzer (SPAN), page 7 • Example of Virtual Interface Configuration Changes, page 9 • Upgrading from Cisco NX-OS 4.0(0)-Based Releases, page 10 • Downgrading to Cisco NX-OS 4.0(0)-Based Releases, page 10 EtherChannel® Upgrade/Downgrade Changes The following table describes the changes to the security ACLs for EtherChannel members. 4.0(0)-based releases 4.0(1a)N1(1a) Upgrade Downgrade Configuration is allowed on member ports (but not used while the port is a member of the EtherChannel). No configuration is allowed on member ports. All member ports follow the configuration on the EtherChannel. Member port ACL configuration, if any, is lost; EtherChannel configuration is preserved. No impact on the functional behavior while the port is a member of the EtherChannel. When the member port leaves the EtherChannel, you have to recreate the ACL configuration on the physical interface. No issue. OL-16601-01 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) 5