Cisco AP775A - Nexus Converged Network Switch 5010 릴리스 노트 - 페이지 9
{카테고리_이름} Cisco AP775A - Nexus Converged Network Switch 5010에 대한 릴리스 노트을 온라인으로 검색하거나 PDF를 다운로드하세요. Cisco AP775A - Nexus Converged Network Switch 5010 26 페이지. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Cisco AP775A - Nexus Converged Network Switch 5010에 대해서도 마찬가지입니다: 릴리스 노트 (48 페이지), 릴리스 노트 (44 페이지), 릴리스 노트 (26 페이지), 빠른 참조 매뉴얼 (14 페이지)
페이지 인쇄
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
•
•
Caveats
This section includes the following topics:
•
•
•
•
•
•
•
•
Open Caveats
This section lists the open caveats for this release.
•
•
OL-16601-01
11 and the switch port 1/5 sends multicast traffic on VLAN 11 in a multicast group, and hosts
connected to FEX ports 100/1/3-12 are interested in receiving that mutlicast traffic (through IGMP),
then that multicast traffic goes out on FEX ports 100/1/3-12, but not on 100/1/1-2.
If you configure SPAN Tx on port 100/1/1, although the multicast traffic does not egress out of port
100/1/1, the SPAN destination does receive that multicast traffic. This is due to a design limitation.
When a FEX port is configured as both SPAN rx-source and tx-source, the broadcast, non-IGMP
layer-2 multicast, and unknown unicast frames originating from that port may be seen twice on the
SPAN destination, once on the ingress and once on the egress path. On the egress path, the frames
are filtered by the FEX to prevent them from going out on the same port on which they were
received. For example, if FEX Port 100/1/1 is configured on VLAN 11, and is also configured as
SPAN rx-source and tx-source and a broadcast frame is received on that port, the SPAN destination
recognizes two copies of the frame, even though the frame is not sent back on port 100/1/1.
A FEX port can not be configured as a SPAN destination. Only a switch port can be configured and
used as a SPAN destination.
Open Caveats, page 9
CSCsz93815
Symptom: After you downgrade from release 4.1(3)N1, the QoS configuration is not restored if the
class-map name is dfferent for type qos, network-qos,or queuing policy-maps.
Workaround: Make sure the class-names between different policy types are the same before you
begin downgrade.
CSCsz82199
Symptom: You cannot enable std.pause on a port-channel interface connected between two Cisco
Nexus 5000 Series switches. Enable std.pause between two Cisco Nexus 5000 Series switches and
configure std.pause in the hardware.
Workaround: None
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
Caveats
9