Cisco AP776A - Nexus Converged Network Switch 5020 릴리스 노트 - 페이지 25

{카테고리_이름} Cisco AP776A - Nexus Converged Network Switch 5020에 대한 릴리스 노트을 온라인으로 검색하거나 PDF를 다운로드하세요. Cisco AP776A - Nexus Converged Network Switch 5020 26 페이지. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Cisco AP776A - Nexus Converged Network Switch 5020에 대해서도 마찬가지입니다: 릴리스 노트 (48 페이지), 릴리스 노트 (44 페이지), 릴리스 노트 (26 페이지), 릴리스 노트 (22 페이지), 빠른 참조 매뉴얼 (14 페이지), 릴리스 노트 (3 페이지)

Cisco AP776A - Nexus Converged Network Switch 5020 릴리스 노트
S e n d d o c u m e n t a t i o n c o m m e n t s t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1a)
This section lists the resolved caveats for this release.
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1)
This was the first release of Cisco NX-OS for Nexus 5000 Series switches. There are no resolved caveats
for this release.
OL-16601-01
CSCsq39683
Symptom: Fibre Channel links with traffic running on it might generate syslog errors such as the
following:
2008 May 21 15:08:55 switch %KERN-3-SYSTEM_MSG: FCP_ERRFCP_PORT:
gat_fcp_isr_process_blk_intr@1441, jiffies = 0xb1cec:ISR threshold reached, reg_block
= 0x8, num_regs = 6, idx = 0, src_bit = 11 - kernel
There is no loss in functionality and these messages can be ignored.
Workaround: None.
CSCso83662
Symptom: One global MAC address is used in all STP and PVRST frames originating on various
ports. This can result in inconsistent MAC moves on peer switches connected with multiple links.
Workaround: None.
CSCsq53614
Symptom: Ethernet port channels configured between two Cisco Nexus 5000Series switches cause
a memory leak in the DCBX process. This leak eventually leads to the DCBX process crashing and
a system reboot (in a few days). This issue occurs only with Ethernet port channels between Cisco
Nexus 5000 Series switches. Port channels using the Catalyst 6500 Series switches do not have this
problem.
Workaround: Disable receive and transmit Link Layer Discovery Protocol (LLDP) on the port
channel members by entering the following configuration under each Ethernet interface that is a
member of the port channel:
Interface Ethernet 1/1
no lldp receive
no lldp transmit
CSCsq36609
Symptom: For a virtual Ethernet or virtual Fibre Channel interface configured as a SPAN source,
changing the interface administrative state results in a memory leak. Deleting and adding SPAN
sessions also causes memory leaks. The memory leaks eventually cause a switch reboot.
Workaround: Avoid using virtual Ethernet and virtual Fibre Channel interfaces as SPAN sources.
Avoid deleting and adding SPAN sessions.
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
Caveats
25