
Patch 86261-09 For Rapier and AT-8800 Series Switches 11
Patch 86261-09 for Software Release 2.6.1
C613-10388-00 REV J
Notifications and triggers for some Firewall events were generated only
when its threshold levels were exceeded. They are now generated whenever
the threshold levels are reached. The affected events are:
SMURFATTACK, TCPTINY, FRAGMENT, LANDATTACK,
IPSPOOFATTACK, PINGOFDEATHATTACK, SPAMATTACK,
RELAYATTACK, SMURFAMPATTACK, OTHERATTACK, RELAYATTACK
When the set switch mirror command was used to configure a port
belonging to more than the default VLAN, the command would fail and an
error message would be produced. However, the port would maintain its
incorrectly mirrored condition, rather than return to its previous
unmirrored condition. This issue has been resolved.
Although all changes to the maxbandwidth parameter of the create qos
policy command were previously accepted, the Rapier’s implementation of
this parameter was inconsistently applied for values that were not exact
multiples of 1 Mbps. This issue has been resolved by ensuring that this
parameter’s value is always rounded up to the nearest 1 Mbps, and a
warning advising the user is displayed.
When the command delete install=preferred was executed, if file
nvs:gui.ins did not exist, the command would incorrectly create it. To resolve
this issue the command will no longer create this file, and will only write to
it if it exists already.
The behaviour of the set set ipv6 nd interface retrans command was
inconsistent. This resulted in the commands show config dynamic=ipv6
and show ipv6 ndconfig not displaying their output. This issue has been
resolved.
If the create dhcp range command was used to try and create an invalid IP
address range that contained an invalid IP address, then the delete dhcp
range command was used to delete the invalid IP address, a fatal exception
error would result. This issue has been resolved.
PCR 40119 introduced an error that prevented tagged VLANs from
operating correctly. Communication between untagged was prevented if
one of the ports was also configured as a tagged port. this issue has been
resolved.
The switch was unable to correctly filter IGMP messages using the L3 filter.
This issue has been resolved.
PCR: 40158 Module: FIREWALL Level: 3
PCR: 40162 Module: SWI Level: 2
PCR: 40172 Module: QOS Level: 2
PCR: 40174 Module: INSTALL Level: 2
PCR: 40177 Module: IPv6 Level: 3
PCR: 40226 Module: DHCP Level: 2
PCR: 40228 Module: VLAN, SW56 Level: 2
PCR: 40244 Module: IPG Level: 2
Comentários a estes Manuais