Allied Telesis R800 Series manual Patch file details for Patch 86222-18 are listed in Table

12 Patch Release Note

Features in 86222-18

Patch file details for Patch 86222-18 are listed in Table 5:

Table 5: Patch file details for Patch 86222-18.

Base Software Release File	86s-222.rez
Patch Release Date	6-May-2002
Compressed Patch File Name	86222-18.paz
Compressed Patch File Size	342720 bytes

There is no patch release 86222-17 because this patch was withdrawn.

Patch 86222-18 includes all issues resolved and enhancements released in previous patches for Software Release 2.2.2, and the following enhancements:

PCR: 02041 Module: SWI Network affecting: No

In some situations, the switch would stop forwarding packets via internal and/or external uplink ports. This issue has been resolved.

PCR: 02073 Module: FILE Network affecting: No

If a flash write error occurred when a file was being written, the file’s directory entry was deleted leaving a partial file in flash. Subsequent attempts to write the file failed because a file of the same name already existed. This issue has been resolved.

PCR: 02075 Module: OSPF, IPG Network affecting: No

In configurations containing a large number of OSPF routes, the SPF calculation could take a long time. During this calculation, other events would not be processed. This patch reduces the time required for an SPF calculation and allows the switch to respond to other events in the mean time. This patch also improves the performance of flow cache updates.

PCR: 02081 Module: FILE, FFS Network affecting: No

If the FILE module was required to re-write a file, the existing file would be deleted before the size of the new file was known. This issue has been resolved.

PCR: 02082 Module: OSPF Network affecting: Yes

OSPF virtual links running across a single network segment would accept

0.0.0.0as the next hop address. This was inherited by derivative routes, making them unusable. This issue has been resolved.

PCR: 02086 Module: FFS Network affecting: No

If a file ended short of an erase block boundary and a compaction was started, the block in which the file was stored was not erased, causing errors when new files were written. Also, if the last file in the filing system ended on or short of an erase block boundary, and a compaction was started, then compaction would fail. These issues have been resolved.

Patch 86222-22 for Software Release 2.2.2 C613-10319-00 REV U