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

Resolved Caveats-Cisco NX-OS Release 4.0(1a)N1(1), running-config startup-config

Page 19 highlights

Caveats Send documentation comments to [email protected] Workaround: Before downgrading to the Cisco NX-OS 4.0(1a)N1(1) release, remove rules from the roles configuration such that a role does not have more than 67 rules. • CSCsv55655 Symptom: The Cisco Nexus 5000 Series switch Ethernet port is configured in the 1 G mode of operation using the speed 1000 command. It does not advertise and auto-negotiate the flow control configuration. As a result, the link peer does not learn about the capabilities of the Nexus 5000 Series switches and does not enable flow control at its end. Workaround: Disable auto-negotiation on the link peer and enable flow control for flow control to work over the link. • CSCsw39639 Symptom: When a rule that refers to a specific interface name (Ethernet 1/1) is entered in the role definition CLI, the command could hang. Type Ctrl-C to return to the CLI prompt. Workaround: Do not configure rules that refer to specific interfaces in the role definition CLI. • CSCsy09062 Symptom: This is an open caveat in 4.0(0)N1(2a) and 4.0(1a)N1(1) releases. After an upgrade or downgrade if the show startup security command is issued before performing a copy running-config startup-config, the security process could crash. Workaround: 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. • CSCsy08516 Symptom: This is an open caveat in 4.0(0)N1(2a) and 4.0(1a)N1(1) releases. After an upgrade or a downgrade and when the system comes up, users are assigned a network-operator role by default. Workaround: To avoid the problem, reload the switch after an upgrade or a downgrade and after the system comes up. You can then perform the copy running-config startup-config operation to save the correct configuration. Resolved Caveats-Cisco NX-OS Release 4.0(1a)N1(1) This section lists the resolved caveats for this release. • CSCsy37432 Symptom: This is an open caveat in the Cisco NX-OS 4.0(0)N1(2a) release. On the 4.0(0)N1(2a) release if an RBAC role has more than 35 rules configured, show running-config and copy running-config cause the vshd process to core dump. Workaround: Before downgrading to the Cisco NX-OS 4.0(0)N1(2a) release, remove rules from the roles configuration such that a role does not have more than 35 rules. • CSCsy53275 Symptom: This is an open caveat in the Cisco NX-OS4.0(0)N1(2a) release. If there are 20 RBAC roles configured with 20 rules each, the RBAC feature becomes non-functional. Workaround: Do not configure more than 20 rules in each role. The feature works fine if the numbers of rules are limited to 10 per role. OL-16601-01 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) 19

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26

Send documentation comments to [email protected]
19
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
Caveats
Workaround:
Before downgrading to the Cisco NX-OS 4.0(1a)N1(1) release, remove rules from
the roles configuration such that a role does not have more than 67 rules.
CSCsv55655
Symptom
: The Cisco Nexus 5000 Series switch Ethernet port is configured in the 1 G mode of
operation using the
speed 1000
command. It does not advertise and auto-negotiate the flow control
configuration. As a result, the link peer does not learn about the capabilities of the Nexus 5000
Series switches and does not enable flow control at its end.
Workaround:
Disable auto-negotiation on the link peer and enable flow control for flow control to
work over the link.
CSCsw39639
Symptom
: When a rule that refers to a specific interface name (Ethernet 1/1) is entered in the role
definition CLI, the command could hang. Type
Ctrl-C
to return to the CLI prompt.
Workaround:
Do not configure rules that refer to specific interfaces in the role definition CLI.
CSCsy09062
Symptom
: This is an open caveat in 4.0(0)N1(2a) and 4.0(1a)N1(1) releases. After an upgrade or
downgrade if the
show startup security
command is issued before performing a
copy
running-config startup-config,
the security process could crash.
Workaround:
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.
CSCsy08516
Symptom
: This is an open caveat in 4.0(0)N1(2a) and 4.0(1a)N1(1) releases. After an upgrade or a
downgrade and when the system comes up, users are assigned a network-operator role by default.
Workaround:
To avoid the problem, reload the switch after an upgrade or a downgrade and after
the system comes up. You can then perform the
copy running-config startup-config
operation to
save the correct configuration.
Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1)
This section lists the resolved caveats for this release.
CSCsy37432
Symptom
: This is an open caveat in the Cisco NX-OS 4.0(0)N1(2a) release. On the 4.0(0)N1(2a)
release if an RBAC role has more than 35 rules configured,
show running-config
and
copy
running-config
cause the vshd process to core dump.
Workaround:
Before downgrading to the Cisco NX-OS 4.0(0)N1(2a) release, remove rules from
the roles configuration such that a role does not have more than 35 rules.
CSCsy53275
Symptom
: This is an open caveat in the Cisco NX-OS4.0(0)N1(2a) release. If there are 20 RBAC
roles configured with 20 rules each, the RBAC feature becomes non-functional.
Workaround:
Do not configure more than 20 rules in each role. The feature works fine if the
numbers of rules are limited to 10 per role.