Cisco 3020 - Cisco Catalyst Blade Switch Примечание к выпуску - Страница 8

Просмотреть онлайн или скачать pdf Примечание к выпуску для Переключатель Cisco 3020 - Cisco Catalyst Blade Switch. Cisco 3020 - Cisco Catalyst Blade Switch 21 страница. 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 страниц), Quickspecs (12 страниц), Примечание к выпуску (41 страниц), Примечание к выпуску (27 страниц), Примечание к выпуску (23 страниц), Руководство по установке (21 страниц)

Cisco 3020 - Cisco Catalyst Blade Switch Примечание к выпуску
Limitations and Restrictions
Dynamic ARP Inspection
This is the Dynamic Arp Inspection limitation:
When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is
within the configured rate limit, the port might go into an error-disabled state. (CSCse06827)
Ethernet
These are the Ethernet limitations:
IP
This is the IP limitation:
When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response
time might be slow when you are using the console. The workaround is to use rate limiting on DHCP
traffic to prevent a denial of service attack from occurring. (CSCeb59166)
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(44)SE
8
When port security is enabled on an interface in restricted mode and the switchport block unicast
interface command has been entered on that interface, MAC addresses are incorrectly forwarded
when they should be blocked
The workaround is to enter the no switchport block unicast interface configuration command on
that specific interface. (CSCee93822)
A traceback error occurs if a crypto key is generated after an SSL client session.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch.
(CSCef59331)
Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports
are distributed to member ports on load balance configuration and traffic characteristics like MAC
or IP address. More than one traffic stream might map to same member ports, based on hashing
results calculated by the ASIC.
If this happens, traffic distribution is uneven on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel
can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip
for incrementing source-ip traffic, configure load balance method as src-ip
for incrementing dest-ip traffic, configure load balance method as dst-ip
Configure the number of ports in the EtherChannel so that the number is equal to a power of 2
(for example, 2, 4, or 8)
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP
addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is
optimal. (CSCeh81991)
If you enter the test cable-diagnostics tdr privileged EXEC command on the dual-media interfaces
Gi0/23 and Gi0/24, the Ethernet interface that is being tested shuts down and then comes back up.
There is no workaround.(CSCse04563)
OL-14761-01