Cisco 3020 - Cisco Catalyst Blade Switch 릴리스 노트 - 페이지 10

{카테고리_이름} Cisco 3020 - Cisco Catalyst Blade Switch에 대한 릴리스 노트을 온라인으로 검색하거나 PDF를 다운로드하세요. Cisco 3020 - Cisco Catalyst Blade Switch 41 페이지. Release notes for the cisco catalyst blade switch 3020 for hp, ciscoã‚â iosã‚â releaseã‚â 12.2(44)se
Cisco 3020 - Cisco Catalyst Blade Switch에 대해서도 마찬가지입니다: 시작하기 매뉴얼 (37 페이지), 시작하기 매뉴얼 (31 페이지), 빠른 사양 (12 페이지), 릴리스 노트 (27 페이지), 릴리스 노트 (23 페이지), 릴리스 노트 (21 페이지), 설치 매뉴얼 (21 페이지)

Cisco 3020 - Cisco Catalyst Blade Switch 릴리스 노트
Limitations and Restrictions
Trunking
These are the trunking limitations:
VLAN
This is the VLAN limitation:
Device Manager Limitations
These are the Device Manager limitations for this release:
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
10
Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol
(PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local
SPAN session. The workaround is to use the monitor session session_number destination
{interface interface-id encapsulation replicate} global configuration command for local SPAN.
(CSCed24036)
The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link
[ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber.
This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the
frame to an IEEE 802.1Q trunk interface. There is no workaround. (CSCdz33708)
IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a
member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the
output interface for the multicast route entry assigned to the multicast group and an interface in
VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN
interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is
forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no
workaround. (CSCdz42909).
For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might
appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q
frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the
frames are not counted on the interface statistics. There is no workaround. (CSCec35100).
If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000,
the switch can fail.
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
When you are prompted to accept the security certificate and you click No, you only see a blank
screen, and the device manager does not launch.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
When the physical UID LED of the switch is on, it is blue. However, when the image of this LED
on the device manager Front Panel view is on, it is green.
There is no workaround (CSCsd98457).
OL-8918-03