HP Cisco MDS 9120 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Rele - Page 48

Workaround, Symptom, interface cpp

Page 48 highlights

Caveats Send documentation comments to mdsfeedback-doc.com. %KERN-3-SYSTEM_MSG: eth1: error in ethGetNextRxBuf %KERN-3-SYSTEM_MSG: eth1: stop internals failed %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx In rare cases, this issue may result in a kernel panic which causes a supervisor switchover. Workaround: This issue is resolved. • CSCsu38297 Symptom: When performing a Veritas Netbackup database backup (such as a NB Catalog Backup), that requires a separate tape cartridge from the scratch pool (other than regular data backup tapes), the tape barcode is shown as Unknown in the Cisco Key Management Center. Workaround: This issue is resolved. • CSCsu41818 Symptom: Following a system reload with a startup-configuration that had scheduler configurations, none of the scheduler CLI commands are available. When upgrading to Cisco SAN-OS 3.2(1c) from a earlier version, the scheduler is enabled by default. Workaround: This issue is resolved. • CSCsu42003 Symptom: When an FCIP tunnel is configured with IPsec between an MDS 9222i switch and an MDS 9216i switch, it fails to come up if an ACL with TCP permit is configured. This causes a mismatch and causes the security association (SA) policy creation to fail in IPsec on the supervisor. Workaround: This issue is resolved. • CSCsu53299 Symptom: When reloading a switch, a timing condition may cause CFS to enter the handshake before the Routing Information Base (RIB) does. In this instance, CFS will not see any peers, and as a result, CFS-based applications will not communicate with the rest of the fabric. Workaround: This issue is resolved. • CSCsu56780 Symptom: A Solaris iSCSI host generates this error: iscsi: [ID 498442 kern.warning] WARNING: iscsi session(5) protocol error - received unknown itt:0x0 - protocol error. Workaround: This issue is resolved • CSCsu63218 Symptom: In some cases, there may be duplicate entries of a global pWWN and virtual pWWN as identified in the following scenarios: - Switch 1 has a v1and p1 entry and p1 is connected to one of the server interfaces on switch 1. - Switch 2 also has a v1and p1 entry along with a v2 and p2 entry; and, switch 2 is in a different CFS region. - While using Replace on different switch option in the FA wizard, if v1 and p2 is provided in the step4 then, the expected operation won't be performed. Workaround: This issue is Resolved. • CSCsu73264 Symptom: Data Mobility Manager (DMM) uses VSAN 1 for IP communication and it requires interface cpp/1/1 to be configured. If another CPP IP Fibre Channel interface is configured in the same module in a different VSAN, then DMM will not work. Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a) 48 OL-17675-05

  • 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
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54

Send documentation comments to mdsfeedback-doc.com.
48
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a)
OL-17675-05
Caveats
%KERN-3-SYSTEM_MSG: eth1: error in ethGetNextRxBuf %KERN-3-SYSTEM_MSG: eth1: stop
internals failed %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error
in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx
%KERN-3-SYSTEM_MSG: eth1: error in rx
In rare cases, this issue may result in a kernel panic which causes a supervisor switchover.
Workaround
: This issue is resolved.
CSCsu38297
Symptom
: When performing a Veritas Netbackup database backup (such as a NB Catalog Backup),
that requires a separate tape cartridge from the scratch pool (other than regular data backup tapes),
the tape barcode is shown as Unknown in the Cisco Key Management Center.
Workaround
: This issue is resolved.
CSCsu41818
Symptom
: Following a system reload with a startup-configuration that had scheduler
configurations, none of the scheduler CLI commands are available. When upgrading to Cisco
SAN-OS 3.2(1c) from a earlier version, the scheduler is enabled by default.
Workaround
: This issue is resolved.
CSCsu42003
Symptom
: When an FCIP tunnel is configured with IPsec between an MDS 9222i switch and an
MDS 9216i switch, it fails to come up if an ACL with TCP permit is configured. This causes a
mismatch and causes the security association (SA) policy creation to fail in IPsec on the supervisor.
Workaround
: This issue is resolved.
CSCsu53299
Symptom
: When reloading a switch, a timing condition may cause CFS to enter the handshake
before the Routing Information Base (RIB) does. In this instance, CFS will not see any peers, and
as a result, CFS-based applications will not communicate with the rest of the fabric.
Workaround
: This issue is resolved.
CSCsu56780
Symptom
: A Solaris iSCSI host generates this error: iscsi: [ID 498442 kern.warning] WARNING:
iscsi session(5) protocol error - received unknown itt:0x0 - protocol error.
Workaround
: This issue is resolved
CSCsu63218
Symptom
: In some cases, there may be duplicate entries of a global pWWN and virtual pWWN as
identified in the following scenarios:
Switch 1 has a v1and p1 entry and p1 is connected to one of the server interfaces on switch 1.
Switch 2 also has a v1and p1 entry along with a v2 and p2 entry; and, switch 2 is in a different
CFS region.
While using Replace on different switch option in the FA wizard, if v1 and p2 is provided in the
step4 then, the expected operation won’t be performed.
Workaround
: This issue is Resolved.
CSCsu73264
Symptom
: Data Mobility Manager (DMM) uses VSAN 1 for IP communication and it requires
interface cpp
<module>
/1/1
to be configured. If another CPP IP Fibre Channel interface is
configured in the same module in a different VSAN, then DMM will not work.