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

Caveats, Open Caveats - vrf

Page 11 highlights

Caveats Send documentation comments to [email protected] Caveats This section includes the following topics: • Open Caveats, page 11 • Resolved Caveats-Cisco NX-OS Release 4.0(1a)N1(1), page 17 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(2a), page 18 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(2), page 19 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(1a), page 21 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(1), page 21 Open Caveats This section lists the open caveats for this release. • CSCsv81694 Symptom: The auto learn static MAC entry is removed if the port on which the same MAC address is dynamically learned is flapped. The static MAC address is removed from the software as well as the hardware. Workaround: Re-add the static MAC entry through the CLI. • CSCsv70815 Symptom: The default VRF is the system default for a VRF setting. Ideally, applications using VRF (such as TACACS+) assume a default VRF value if a VRF configuration is not specified by the administrator. However, TACACS+ is not set up properly unless the default VRF is configured. Workaround: The Cisco Nexus 5000 Series switches support two possible VRFs, the default and the management. Configure the desired VRF when using TACACS+ service. You can configure the desired VRF using either of these configurations: aaa group server tacacs+ t1 server 10.193.149.54 use-vrf management aaa group server tacacs+ t2 server 20.1.1.2 use-vrf default • CSCsu01188 Symptom: No traps are sent when SFPs for GE and 10GE are removed or inserted. Workaround: None. • CSCsv55655 Symptom: The Cisco Nexus 5000 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 on its end. Workaround: Disable auto-negotiation on the link peer and enable flow control for flow control to work over the link. OL-16601-01 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) 11

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

Send documentation comments to [email protected]
11
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1)
OL-16601-01
Caveats
Caveats
This section includes the following topics:
Open Caveats, page 11
Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1), page 17
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2a), page 18
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2), page 19
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1a), page 21
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1), page 21
Open Caveats
This section lists the open caveats for this release.
CSCsv81694
Symptom
: The auto learn static MAC entry is removed if the port on which the same MAC address
is dynamically learned is flapped. The static MAC address is removed from the software as well as
the hardware.
Workaround:
Re-add the static MAC entry through the CLI.
CSCsv70815
Symptom
: The default VRF is the system default for a VRF setting. Ideally, applications using VRF
(such as TACACS+) assume a default VRF value if a VRF configuration is not specified by the
administrator. However, TACACS+ is not set up properly unless the default VRF is configured.
Workaround:
The Cisco Nexus 5000 Series switches support two possible VRFs, the default and the management.
Configure the desired VRF when using TACACS+ service. You can configure the desired VRF using
either of these configurations:
aaa group server tacacs+ t1
server 10.193.149.54
use-vrf management
aaa group server tacacs+ t2
server 20.1.1.2
use-vrf default
CSCsu01188
Symptom
: No traps are sent when SFPs for GE and 10GE are removed or inserted.
Workaround:
None.
CSCsv55655
Symptom
: The Cisco Nexus 5000 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 on its end.
Workaround:
Disable auto-negotiation on the link peer and enable flow control for flow control to
work over the link.