Release notes - H3C S9500-CMW310-R1652P03

Hangzhou H3C Technologies Co., Ltd.
H3C S9500-CMW310-R1652P03
Release Notes
2010-9-27 Page 14 of 56
is possible that there is no receiver end in the downstream, and some out interfaces
in the upstream do not prune.
26. Limitation 26
【Multicast】In VRRP/STP networking, Layer-2 multicast packets may be lost during
transparent transmission when Layer-3 multicast table entry is added or removed.
27. Limitation 27
【Performance】Reduce the number of sub-VLANs enabling ARP proxy under the
Super-VLAN. The more sub-VLANs enabling ARP proxy are configured under the
Super-VLAN, the worst the ARP learning performance is.
28. Limitation 28
【Performance】When a large number of users conduct the 802.1X authentication, it
is suggested that the handshake time be prolonged to 180 seconds. Otherwise, as
the number of users passing the authentication grows, part of the online users will be
forced to go offline due to handshake failure.
29. Limitation 29
【Performance】In the case of a great number of EBGP neighbors, the MPU memory
is recommended to be 1G memory; Otherwise, exception will occur in the system. For
example: 1. lots of memory shortage information printed out; 2. the FIB table is
inconsistent with the routing table; 3. finally the memory is used up and the system is
unavailable.
30. Limitation 30
【 Performance】 Load sharing can be implemented only on 2~6 ECMP routes,
except the board with suffixes DB/DC. It is suggested that no more than 6 equivalent
routes be used, or the effect of load sharing will not be good enough.
31. Limitation 31
【Performance】Load sharing can be implemented through link-aggregation of only
2~4 links, except the board with suffixes DB/DC. No more than 4 links should be used
for link-aggregation, or load sharing through link-aggregation will not achieve
satisfactory effect.