Cisco C-series Nexus 5020 Release Release - Pagina 5
Blader online of download pdf Release Release voor {categorie_naam} Cisco C-series Nexus 5020. Cisco C-series Nexus 5020 26 pagina's. Replacing an i/o module nexus 5000 series
Ook voor Cisco C-series Nexus 5020: Specificaties (3 pagina's), Gegevensblad (23 pagina's), Release Release (3 pagina's), Handmatig (11 pagina's), Hardware installatiehandleiding (19 pagina's)
Pagina afdrukken
S e n d d o c u m e n t a t i o n c o m m e n t s t o n e x u s 5 k d o c s @ c i s c o . c o m
•
•
•
•
For more information about the features listed, refer to the documentation set listed in
Documentation" section on page
This section includes the following topics:
•
•
•
•
•
•
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
OL-16601-01
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 <feature> 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.
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
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.
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
26.
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
the"Related
5