Allied Telesis 86253-07 User Manual

Page 10

Advertising
background image

10

Patch Release Note

Patch 86253-07 for Software Release 2.5.3

C613-10382-00 REV E

When the device received a version 1 Query packet, it become a non-querier
on that interface, even if it should have remained as the querier. This issue
has been resolved.

When the TYPE parameter was specified for the ADD SWITCH L3FILTER
command, the type was sometimes a different value in the device’s
hardware table. This issue has been resolved.

The maximum value that the MESSAGES parameter accepted for the
CREATE LOG OUTPUT command was different from the value that could
be set with the SET LOG OUTPUT command. The DESTROY LOG
OUTPUT command did not release the NVS memory that was reserved for
the output. These issues have been resolved.

The etherHistoryIntervalStart node in the etherHistoryTable showed incorrect
values for the first and last 30 second interval periods. This issue has been
resolved.

If a rule based NAT was added to the firewall’s public interface, the firewall
forwarded ICMP Request packets even if ICMP forwarding was disabled.
This issue has been resolved.

When a large number of directed broadcast packets were received, CPU
usage increased up to 100%. This occurred because a log message was
generated each time a directed broadcast packet was deleted. This issue has
been resolved. Log messages are now rate-limited to a maximum of one log
message every 10 seconds for a directed broadcast flow. After the first
deletion is logged, subsequent log messages include a counter showing the
number of directed broadcast packets in the same flow that were deleted
since the last log message.

A fatal error occurred if IPX was disabled and then re-enabled when there
was a high rate of incoming IPX traffic on the device. This issue has been
resolved.

The DHCP server did not take any action when it received a DHCP decline
packet. This was because the device only checked the ciaddr field in the
packet, and not the RequestedIPAddress option. This issue has been resolved.

This PCR introduces an enhancement that extends an issue that was
resolved in PCR 03890, in which switch port entries are only created for
special router multicast addresses. It is now possible to specify reserved
multicast addresses that will be treated as multicast packets from routers.
Use the following commands to configure this feature.

PCR: 31106

Module: MLD

Level: 2

PCR: 31118

Module: SWI

Level: 2

PCR: 31119

Module: LOG

Level: 2

PCR: 31122

Module: RMON

Level: 3

PCR: 31127

Module: FIREWALL

Level: 2

PCR: 31128

Module: IPG

Level: 2

PCR: 31129

Module: IPX2

Level: 2

PCR: 31132

Module: DHCP

Level: 2

PCR: 31133

Module: IPG

Advertising