Allied Telesis AR800 Series - Manual (Page 15)

Patch 86231-10 For Rapier Switches and AR800 Series Modular Switching Routers 15
Patch 86231-10 for Software Release 2.3.1
C613-10328-00 REV J
• Multiple TTY sessions could edit the same file. This caused
unpredictable behaviour when the TTY sessions closed the files.
A new command, SHOW FFILE VERIFY, has been added. This command
steps through the file system headers starting with file zero and finishing at
the end of the last reachable file. It then verifies that all FLASH locations
from the end of the last reachable file to the beginning of file zero are in an
erased state. Errors are reported as they are found.
The SHOW CONFIG DYNAMIC=VRRP command was not showing port
monitoring and step values correctly. This issue has been resolved.
When VRRP responded to an ARP request for the VR IP address it was not
making an entry in the ARP table and the switch L3 table. This issue has
been resolved.
Untagged Layer 2 packets selected for mirroring were incorrectly
transmitted from the mirror port with a tag. This issue has been resolved.
If a port on a Rapier 48 or Rapier 48i went down, some associated entries
were not promptly removed from the forwarding, Layer 3 and default IP
tables. This issue has been resolved.
This PCR includes the following enhancements:
• A new command, SET DHCP EXTENDID allows for multiple DHCP
clients, and handling of arbitrary client IDs on the server.
• Static DHCP entries now return to the correct state when timing out.
• DHCP entry hashes now have memory protection to prevent fatal
errors.
• DHCP client now retransmits XID correctly.
• Lost OFFER messages on the server are now handled correctly.
The DHCP server now correctly handles DHCP clients being moved to a
different interface on the DHCP server after they’ve been allocated an IP
address.
The CPU and MEMORY parameters in the SET TRIGGER command
erroneously accepted the minimum value “0” rather than “1”. This issue has
been resolved.
Previously, when Firewall or IP NAT was enabled, any fragmented IP
packets had to be reassembled so they could be processed. If the fragments
could not be reassembled, the packet was dropped. Reassembly could only
occur if the combined packet (IP header, and protocol header, and data) was
no more than 1800 bytes. An additional limit of no more than eight
fragments was also imposed. This PCR implements enhanced fragment
PCR: 02185 Module: VRRP Network affecting: No
PCR 02188 Module: VRRP Network affecting: No
PCR 02194 Module: SWI Network affecting: No
PCR: 02195 Module: SWI Network affecting: No
PCR: 02198 Module: DHCP Network affecting: Yes
PCR: 02199 Module: TRIGGER Network affecting: No
PCR: 02202 Module: FIREWALL/IP NAT Network affecting: No