HP Cisco MDS 9020 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Rele - Page 44

Workaround, Symptom, logging log

Page 44 highlights

Caveats Send documentation comments to [email protected] Workaround: This issue is resolved. • CSCsz84022 Symptom: The TPC application cannot discover the MDS 9509 switch when it is connected to an MDS 9020 switch. Workaround: This issue is resolved. • CSCsz95999 Symptom: A kernel failure in the Mgmt0 driver caused the MDS 9222i switch to reboot Workaround: This issue is resolved. • CSCta08796 Symptom: A memory leak caused the port manager to fail and put the ports in a hardware failure state. Workaround: This issue is resolved. • CSCta15575 Symptom: The SystemName property on the CIM Server is returning the wrong values for N port and F port. Workaround: This issue is resolved. • CSCta28642 Symptom: SNMP should gracefully handle timeouts caused by port initialization. Workaround: This issue is resolved. • CSCta34629 Symptom: The system manager core server does not clean up the core files on the MDS 9513 switch. Workaround: This issue is resolved. • CSCtb29470 Symptom: A large sequence number causes Performance Manager in Web Client to not function properly. Workaround: This issue is resolved. • CSCtb62488 Symptom: Port flaps during a zone set activation cause the zone set to get stuck with the status: Activation in progress. Workaround: This issue is resolved. • CSCsw87910 Symptom: When running Cisco MDS Release SAN-OS 3.3(2) with DPVM enabled, if a link flaps for a end device with DPVM enabled, you might see the following message in the output of the show logging log command: %DPVM-3-PSS_ERR: Failed to update Login info NPV contextpwwn: 50:00:00:00:aa:99:ee:44, syserr = no such pss key Workaround: This issue is resolved. • CSCta32005 Symptom: Upon receiving an OLS when a link went down, the OLS counter was not incremented. Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a) 44 OL-19964-02

  • 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
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48

Send documentation comments to [email protected]
44
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a)
OL-19964-02
Caveats
Workaround
: This issue is resolved.
CSCsz84022
Symptom
: The TPC application cannot discover the MDS 9509 switch when it is connected to an
MDS 9020 switch.
Workaround
: This issue is resolved.
CSCsz95999
Symptom
: A kernel failure in the Mgmt0 driver caused the MDS 9222i switch to reboot
Workaround
: This issue is resolved.
CSCta08796
Symptom
: A memory leak caused the port manager to fail and put the ports in a hardware failure
state.
Workaround
: This issue is resolved.
CSCta15575
Symptom
: The SystemName property on the CIM Server is returning the wrong values for N port
and F port.
Workaround
: This issue is resolved.
CSCta28642
Symptom
: SNMP should gracefully handle timeouts caused by port initialization.
Workaround
: This issue is resolved.
CSCta34629
Symptom
: The system manager core server does not clean up the core files on the MDS 9513
switch.
Workaround
: This issue is resolved.
CSCtb29470
Symptom
: A large sequence number causes Performance Manager in Web Client to not function
properly.
Workaround
: This issue is resolved.
CSCtb62488
Symptom
: Port flaps during a zone set activation cause the zone set to get stuck with the status:
Activation in progress.
Workaround
: This issue is resolved.
CSCsw87910
Symptom
: When running Cisco MDS Release SAN-OS 3.3(2) with DPVM enabled, if a link flaps
for a end device with DPVM enabled, you might see the following message in the output of the
show
logging log
command:
%DPVM-3-PSS_ERR: Failed to update Login info NPV contextpwwn:
50:00:00:00:aa:99:ee:44, syserr = no such pss key
Workaround
: This issue is resolved.
CSCta32005
Symptom
: Upon receiving an OLS when a link went down, the OLS counter was not incremented.