Allied Telesis 86251-08 Switch User Manual


 
10 Patch Release Note
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Files used during start up were backed up from NVS to FLASH even if they
were already present in FLASH. This used up FLASH memory
unnecessarily. This issue has been resolved so that files are only backed up
when a copy does not already exist in FLASH.
If a configuration file had a long file name, the SHOW CONFIG command
displayed the file name using the shortened DOS 8.3 format (where file
names are 8 characters long, with extensions of 3 characters). This issue has
been resolved so that long configuration file names are now displayed using
the DOS 16.3 format (where file names are up to 16 characters long).
The TIMEOUT and SIZE parameters are only valid for the SET IP DNS
CACHE command, but no error message was returned if either parameter
was specified for the SET IP DNS command. This issue has been resolved.
Fragmentation of IPv6 packets now complies with RFC 2460’s requirement
to align packet sizes to 8 octets.
When a 4-port ETH PIC card was installed, the output of the SHOW IP
INTERFACE command showed the ETH port as Down, but the link LEDs
on the card were lit. This issue has been resolved. The SHOW command
now shows the correct link status. The link will go down after 90 seconds if
no inbound traffic is received. When inbound traffic is received the link will
come up.
Setting RSTPTYPE to NORMAL, when normal has already been set, sets all
ports to the “sending RSTP” state process. This is referred to in IEEE 802.1w
as mCheck.
When RSTPTYPE was changed from STPCOMPATIBLE to NORMAL with
the SET STP command, the STP instance continued to send STP BPDUs
until an mCheck was performed by entering the SET STP
RSTPTYPE=NORMAL command again. This issue has been resolved so
that when RSTPTYPE is set to NORMAL an mCheck is performed, causing
the STP to start sending RSTP BPDUs immediately.
MLD and MLD Snooping accepted MLD Query packets with a hop limit
greater than 1. Duplicate packets were forwarded when the hop limit was
not 1 and the payload was 0::0. This issue has been resolved. MLD and MLD
Snooping now require the hop limit to be 1.
Packets with bad ACK numbers were sometimes generated by the firewall
as part of the proxy TCP setup process. These packets sometimes caused
TCP sessions from the public side of the firewall to fail. This issue has been
resolved.
PCR: 03778 Module: FILE, INSTALL, SCR Level: 2
PCR: 03780 Module: INSTALL Level: 3
PCR: 03783 Module: IPG Level: 3
PCR: 03784 Module: IPV6 Level: 3
PCR: 03789 Module: ETH Level: 2
PCR: 03796 Module: STP Level: 2
PCR: 03801 Module: MLDS Level: 2
PCR: 03802 Module: FIREWALL Level: 1