12
Features in sb275a02
Software Maintenance Release Note
Version sb275a05
C613-10464-00 Rev H
Features in sb275a02
Software maintenance version sb275a02 includes all resolved issues and
enhancements in earlier 2.7.5A versions, and the resolved issues and
enhancements in the following tables.
Level 1
No level one issues
Level 2
CR
Module
Level
Description
CR00006503
IP Gateway
2
Large UDP packets sometimes caused a memory corruption, which could
cause unexpected switch behaviour, including reboots.
This issue has been resolved.
CR00012264
IP Gateway
2
Multicast packets were incorrectly being sent to the CPU when the switch
received them on an IP interface that did not have DVMRP or PIM enabled
on it. This could result in unexpectedly high CPU usage statistics.
This issue has been resolved.
CR00012417
Switch, Utility
2
The switch sometimes did not process ARP requests fast enough to
prevent VRRP from changing mastership in the network.
This issue has been resolved.
CR00012455
BOOTP,
IP Gateway
2
When the switch’s BOOTP relay agent relayed a DHCP offer to a locally-
attached DHCP client, the switch added an ARP entry with an incorrect
port number. This meant packets from clients were forwarded by the CPU
instead of being switched in hardware.
This issue has been resolved.
CR00012504
BOOTP
2
There was a synchronisation issue between the software IP ARP table and
the hardware IP table, when a switch was configured for BOOTP relay and
multihoming concurrently. This could cause packets destined for clients to
be forwarded by the CPU or dropped instead of being switched in
hardware.
This issue has been resolved.
CR00012725
IP Gateway,
Switch
2
If a destination could be reached by both an interface route and a backup
route (a static route with the same destination as the network address of
the interface), in some circumstances the switch did not add either route
to its hardware route table. This stopped the switch from sending traffic
via either the interface or the backup route.
This situation has been resolved. The switch now correctly uses the
interface route when the interface is up and the backup route when the
interface is down.
