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

Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(2a

Page 21 highlights

Caveats Send documentation comments to [email protected] • CSCsr39670 Symptom: Although SNMP notification is enabled on the switch, traps for the power supply and fan modules are not received. Workaround: None. • CSCsr47531 Symptom: When a VSAN is configured as SPAN source, traffic from all the member ports is spanned to the SPAN destination port. When a switch is rebooted, the VSAN SPAN source remains in the down state. Workaround: Delete and add the VSAN sources for the SPAN session. Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(2a) • CSCsu08988 Symptom: Telnet access is available only after reloading the Nexus 5020 switch with the no telnet server enable command running. Workaround: Execute the no telnet server enable command once again after reload even if the command is saved in the startup-config. Additionally, you can also apply filters to the SVI to allow only trusted hosts to communicate with the system. • CSCsu32247 Symptom: The Nexus 5000 Series switch executes the power-on self-test (POST) at bootup to validate hardware integrity of the ASICs. When a Fibre Channel port is connected to a host bus adapter (HBA), the HBA driver can trigger a signal loss that causes a false failure to be reported by POST for one of the ASICs. As a result, all the ports serviced by the ASIC on the GEM are marked for hardware failure. Workaround: Do not connect HBAs to the FC expansion modules. • CSCsu40126 Symptom: When the Nexus 5000 Series switch is configured to operate in the N-port virtualization (NPV) mode, the LOGOs received over the server port are not processed properly. This results in stale Fibre Channel IDs at the switch. Workaround: Perform shut and no shut command operations on all the server ports to clear the stale state on the NPV switch. • CSCsm66194 and CSCsr66209 Symptom: Logins may not be uniformly balanced across all available border ports when the Nexus 5000 series switch operates in the NPV mode under conditions such as the following: • The switch is reloaded. • NPIV is disabled and re-enabled on the NPV core-switch. • The NPV core-switch is reloaded. • A new NP link is added. Workaround: Perform shut and no shut command operations on all the server ports to rebalance the logins. • CSCsu25775 Symptom: When the Nexus 5020 Series switch is connected to a 110 V power supply, the following problems occur: OL-16601-01 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) 21

  • 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]
21
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
Caveats
CSCsr39670
Symptom
: Although SNMP notification is enabled on the switch, traps for the power supply and fan
modules are not received.
Workaround
: None.
CSCsr47531
Symptom
: When a VSAN is configured as SPAN source, traffic from all the member ports is
spanned to the SPAN destination port. When a switch is rebooted, the VSAN SPAN source remains
in the down state.
Workaround
: Delete and add the VSAN sources for the SPAN session.
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2a)
CSCsu08988
Symptom
: Telnet access is available only after reloading the Nexus 5020 switch with the
no telnet
server enable
command running.
Workaround:
Execute the
no telnet server enable
command once again after reload even if the
command is saved in the startup-config. Additionally, you can also apply filters to the SVI to allow
only trusted hosts to communicate with the system.
CSCsu32247
Symptom
: The Nexus 5000 Series switch executes the power-on self-test (POST) at bootup to
validate hardware integrity of the ASICs. When a Fibre Channel port is connected to a host bus
adapter (HBA), the HBA driver can trigger a signal loss that causes a false failure to be reported by
POST for one of the ASICs. As a result, all the ports serviced by the ASIC on the GEM are marked
for hardware failure.
Workaround:
Do not connect HBAs to the FC expansion modules.
CSCsu40126
Symptom
: When the Nexus 5000 Series switch is configured to operate in the N-port virtualization
(NPV) mode, the LOGOs received over the server port are not processed properly. This results in
stale Fibre Channel IDs at the switch.
Workaround:
Perform
shut
and
no shut
command operations on all the server ports to clear the
stale state on the NPV switch.
CSCsm66194 and CSCsr66209
Symptom
: Logins may not be uniformly balanced across all available border ports when the Nexus
5000 series switch operates in the NPV mode under conditions such as the following:
The switch is reloaded.
NPIV is disabled and re-enabled on the NPV core-switch.
The NPV core-switch is reloaded.
A new NP link is added.
Workaround:
Perform
shut
and
no shut
command
operations on all the server ports to rebalance
the logins.
CSCsu25775
Symptom
: When the Nexus 5020 Series switch is connected to a 110 V power supply, the following
problems occur: