3COM_OS_SW8800_V3.01.32s256rc13_Release_Notes

3COM OS SW8800 V3.01.32s256rc13 Release Notes
April 25, 2013 Page 10 of 56
Limitation 21
【Multicast】In the case of multicast MSDP trans-domain networking, the static RP (Rendezvous
Point) mode should be configured. Otherwise, RP dynamic switchover will make MSDP unable to
send the SA (Source Active) messages across the domains.
Limitation 22
【Multicast】If the ECMP routes exist on the upstream and downstream switches, the ASSERT
mechanism is not supported, in which case the PIM SM is recommended. Otherwise, many copies of
multicast packets will impact the downstream switch running PIM DM.
Limitation 23
【Multicast】The multicast flows with IP address ranges as X.0.0.X, X.128.0.X, X.0.1.1 and X.128.1.1
are sent to the CPU for processing as the protocol packets. So such IP addresses cannot be used as
our multicast addresses. Otherwise, the entries of these multicast addresses cannot be established
normally, which will cause multicast forward failure.
Limitation 24
【Multicast】In case of large traffic, the duplication capability of the trunk port is only 35 copies. If
multicast packets need to be copied to over 35 VLANs from the one port, the multicast VLAN is
recommended, or packet loss may occur during packet forwarding.
Limitation 25
【Multicast】In the PIM DM mode, it is suggested that the number of the multicast flows in the same
group, but from different sources, be no more than 64. Otherwise, it is possible that there is no
receiver end in the downstream, and some out interfaces in the upstream do not prune.
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.
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.
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.