3COM_OS_SW8800_V3.01.32rc13_Release_Notes

3COM OS SW8800 V3.01.32rc13 Release Notes
April 25, 2013 Page 12 of 56
Limitation 37
【Board】On the 3C17532/3C17528/3C17532A/3C17528A board, an Access or Hybrid untagged port
cannot serve for mirroring source port; Otherwise, the mirrored packets may be incorrectly tagged. As
a result, some network adapters cannot identify the packets.
Limitation 38
【NetStream】NetStream does not create traffic flow entry for the first packet with the TCP RST flag
or FIN flag, and the system cannot take statistics about TCP RST packets or FIN packets without
corresponding traffic flow entries.
Limitation 39
【NetStream】In the case that there exist equal-cost routes or policy routes, the next hop or AS
number may be incorrect in the NetStream statistics.
Limitation 40
【NetStream】Packet statistics log transmission is delayed because the statistics information is
collected by the NetStream board every a specified interval.
Limitation 41
【NetStream】The NetStream board does not support collecting statistics of MPLS traffic by labels on
the outgoing interface at the public network side when the SW8800 functions as a PE.
Limitation 42
【 OSPF 】 SW8800 OSPF cannot calculate COST value of VLAN interface according to link
bandwidth. To distinguish link priority, please specify a COST value for the VLAN interface.
Limitation 43
【Portal】Do not enable portal authentication on the VLAN interface of an aggregated port. Otherwise,
the successfully authenticated user connections may be tore down forcibly after the port aggregation
is canceled.
Limitation 44
【IP protection】If active/standby MPU switchover occurs, do not immediately (at least within 5
minutes) disable the IP protection function on an IP-protection-enabled VLAN interface. Otherwise,
Layer 3 forwarding may not function normally.
Limitation 45
【Upgrade】In the original customized traffic flow template, Ethernet type field is defined and the
template length is 15/16 bytes. Upgrading from Jalpa version, template configuration recovery may be
failed because the traffic flow template exceeds 16 bytes in length.