3COM_OS_SW8800_V3.01.32s256rec13_Release_Notes

3COM OS SW8800 V3.01.32s256rec13 Release Notes
April 25, 2013 Page 11 of 70
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.
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.
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.
Limitation 32
【Performance】On the same port of the board with suffixes B, it is suggested that the number of
delivered ACL configuration rules be no greater than 64. Otherwise, on the port, forwarding speed
cannot reach line speed.
Limitation 33
【Performance】Do not use regular expression in commands to check the system configuration if the
system has a large number of configuration items. For example, the display current-configuration |
include regular-expression command may cause high CPU utilization, thus affecting packets
exchange of the local device.
Limitation 34
【Board】Do not insert a 4-port 10GE board, such as 3C17526/3C17536, into slot 1 or last slot in the
SW8814 chassis, because these boards require higher heat dissipation conditions.
Limitation 35
【Board】3C17526 do not support the following items: WAN mode, aggregation, port isolation, traffic
mirroring, traffic shaping, ACL by VLAN .
Limitation 36
【Board】The 48Port boards 3C17532/3C17528/3C17532A/3C17528A cannot be used for the VLL
(Virtual Leased Line) with board intermixing, or the packets from the public network side will be
dropped, resulting in service forward failure.