Patch | 19 |
PCR: 02008 | Module: TRIGGER | Network affecting: No |
The first periodic after day trigger boundary (i.e. midnight) did not occur. A range check error occurred due to an incorrect comparison. These issues have been resolved.
PCR: 02011 | Module: PING | Network affecting: No |
Stopping a trace route using STOP TRACE occasionally caused a fatal error.
This issue has been resolved.
PCR: 02012 | Module: IPG, VLAN, SWI | Network affecting: No |
IGMP reflooded packets with VLAN tagging were not processed correctly.
This issue has been resolved.
Features in
Patch file details for Patch
Table 11: Patch file details for Patch
Base Software Release File | |
|
|
Patch Release Date | |
|
|
Compressed Patch File Name | |
|
|
Compressed Patch File Size | 296244 bytes |
|
|
Patch
PCR: 01243 | Module: SWI | Network affecting: No |
When a Rapier CPU was handling a large amount of traffic and a busy egress port went down, it was possible for the transmission of packets by the CPU to cease. This issue has been resolved.
PCR: 01265 | Module: SWI | Network affecting: No |
When trunking was in operation, in some instances the switch transmitted tagged packets on untagged trunk ports. This issue has been resolved.
PCR: 01288 | Module: SWI | Network affecting: No |
When a switch port was forced to half duplex mode and the link partner was forced to full duplex mode, it was possible for the switch to enter a state where it was unable to transmit packets. This issue has been resolved.
Patch