Allied Telesis SB251-13 - Manual (Page 4)

4 Patch Release Note
Patch SB251-13 for Software Release 2.5.1
C613-10361-00 REV M
The SET VLAN BCLIMIT command did not work when executed from
start-up in a configuration script. This issue has been resolved.
New static routes cannot be added to the forwarding database until ARP
has resolved the routes' next hop MAC address. In the meantime, selecting
the best alternative route was sometimes causing incorrect forwarding and
loops. To avoid this situation, packets destined for dead-end routes are now
forced to the CPU. The CPU then creates an ICMP_Redirect message to the
source of the unforwardable packet to remove the previous hop from its
routing table.
In order to force packets back to the CPU, the hardware MAC table contains
a special entry for each VLAN that maps the unused MAC address
55.55.55.55.55.55.55.55 to the Multicast Group ID 4096. When the switch
encounters an unknown next hop MAC address, it now sends the packet to
the L2MC Group 4096. Because this group does not exist, the packet is
forwarded to the CPU. Note that this process will increment the SHOW
SWITCH COUNTER command’s L2MCGroupSoesntExist counter.
When a user logged on twice, thus creating two sessions, the user log on
time for the second session was overwriting the value recorded for the first.
This issue has been resolved by displaying the log on times as two separate
sessions.
Previous STP ports were not being deleted correctly when line cards were
hot swapped. Also STP ports were not initialising correctly when STP was
not enabled. These issues have been resolved.
With static multicasting enabled on two VLANs, only the first few multicast
packets of a stream were L3 forwarded. This issue has been resolved.
The copying of switch routes between internal components was causing
processing delays. This issue has been resolved.
Although the SwitchBlade hardware is capable of forwarding jumbo
frames, sending these to the CPU was causing a variety of issues. These
issues have been resolved.
Attempts to disable BGP debug were, depending on configuration,
resulting in either a system failure, or the debug messages continuing to
appear after debug had been disabled. This issue has been resolved.
PCR: 03524 Module: OSPF, IPG Level: 2
PCR: 03717 Module: IP, SWCX Level: 2
PCR: 03726 Module: TTY, USER Level: 3
PCR: 03727 Module: SWI, STP Level: 2
PCR: 03734 Module: IPG Level: 2
PCR: 03736 Module: IPG Level: 3
PCR: 03739 Module: SWI Level: 2
PCR: 03746 Module: BGP Level: 3