HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 12

Workaround, Symptom, no shut, system qos service-policy, class-default, class-fcoe

Page 12 highlights

Caveats Send documentation comments to [email protected] Workaround: None. This is a display issue only. • CSCsx68778 Symptom: You cannot configure commands under the interface range Workaround: Configure command sunder HIF ports of one FEX at a time. • CSCsx60187 Symptom: Duplicate IP addresses are configured for multiple SVI interfaces. Workaround: Do not configure two more SVIs with the same IP address. • CSCsx35870 Symptom: The CLI times out when large number of VLANs are created and deleted followed by PVLAN creation and deletion. The system will syslog indicating that Ethernet Port Manager (ethpm) timing out to communicate with SPAN manager or PVLAN manager. As a result, some of the PVLAN interfaces will be error disabled. FEX ports are configured as a member of PVLAN and some of them are member of regular VLAN. Workaround: Perform shut and no shut on the error disabled interfaces. • CSCsx40562 Symptom: ACL drop traffic with 802.1p cos values greater than 3 may not get spanned if all four user qos classes are not configured in system qos service-policy configuration.e Workaround: Configure all four user qos classes (except class-default and class-fcoe) under system qos service-policy to span all ACL drop traffic. • CSCsw21301 Symptom: Cisco NX-OS does not provide offline configuration support. The creation of a FEX interface depends on the FEX coming online after a fabric interface configuration. When you restore configuration from a file, there periodwhen FEX interfaces are not yet created but interface configuration is applied and fails. Workaround: If system configuration is to be restored from a configuration file (copied locally or through tftp), you can separate the FEX interface part of the configuration (if any) into a different file. Copy the main file first, then wait for FEX to come online, and then copy the separate FEX interface configuration file. Alternately, you can copy twice. • CSCsv93263 Symptom: Cisco NX-OS does not provide offline configuration support. The creation of a FEX interface depends on the FEX coming online after a fabric interface configuration. When you restore configuration from a file, there periodwhen FEX interfaces are not yet created but interface configuration is applied and fails. Workaround: If system configuration is to be restored from a configuration file (copied locally or through tftp), you can separate the FEX interface part of the configuration (if any) into a different file. Copy the main file first, then wait for FEX to come online, and then copy the separate FEX interface configuration file. Alternately, you can copy twice. • 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. Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1) 12 OL-16601-01

  • 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]
12
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Caveats
Workaround:
None. This is a display issue only.
CSCsx68778
Symptom
: You cannot configure commands under the interface range
Workaround:
Configure command sunder HIF ports of one FEX at a time.
CSCsx60187
Symptom
: Duplicate IP addresses are configured for multiple SVI interfaces.
Workaround:
Do not configure two more SVIs with the same IP address.
CSCsx35870
Symptom
: The CLI times out when large number of VLANs are created and deleted followed by
PVLAN creation and deletion. The system will syslog indicating that Ethernet Port Manager
(ethpm) timing out to communicate with SPAN manager or PVLAN manager. As a result, some of
the PVLAN interfaces will be error disabled. FEX ports are configured as a member of PVLAN and
some of them are member of regular VLAN.
Workaround:
Perform
shut
and
no shut
on the error disabled interfaces.
CSCsx40562
Symptom
: ACL drop traffic with 802.1p cos values greater than 3 may not get spanned if all four
user qos classes are not configured in
system qos service-policy
configuration.e
Workaround:
Configure all four user qos classes (except
class-default
and
class-fcoe
) under
system qos service-policy
to span all ACL drop traffic
.
CSCsw21301
Symptom
: Cisco NX-OS does not provide offline configuration support.
The creation of a FEX
interface depends on the FEX coming online after a fabric interface configuration. When you restore
configuration from a file, there periodwhen FEX interfaces are not yet created but interface
configuration is applied and fails.
Workaround:
If system configuration is to be restored from a configuration file (copied locally or
through tftp), you can separate the FEX interface part of the configuration (if any) into a different
file.
Copy the main file first, then wait for FEX to come online, and then copy the separate FEX
interface configuration file.
Alternately, you can copy twice.
CSCsv93263
Symptom
: Cisco NX-OS does not provide offline configuration support.
The creation of a FEX
interface depends on the FEX coming online after a fabric interface configuration. When you restore
configuration from a file, there periodwhen FEX interfaces are not yet created but interface
configuration is applied and fails.
Workaround:
If system configuration is to be restored from a configuration file (copied locally or
through tftp), you can separate the FEX interface part of the configuration (if any) into a different
file.
Copy the main file first, then wait for FEX to come online, and then copy the separate FEX
interface configuration file.
Alternately, you can copy twice.
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.