Software Version sb275a05
7
Version sb275a05
C613-10464-00 Rev H
CR00011585
OSPF
2
Adding the same OSPF stub or host twice caused OSPF to suspend its
operation, causing neighbour relationships to eventually fail.
This issue has been resolved.
CR00012067
OSPF
2
A summary LSA was not turned into a route if the destination and mask
fell inside one of the switch’s active ranges, unless it exactly matched the
active range’s address and mask.
This complied with RFC 1583 section 16.2. However, the recommended
behaviour has been modified in RFC 2328 section 16.2. To comply with
this, the LSA is now calculated if it falls inside one of the switch’s active
ranges.
CR00012606
STP
2
Processing of an invalid STP packet could result in an STP timeout value
being incorrectly set to 0.
This issue has been resolved, so the timeout can never be set to 0.
CR00012783
VLAN
2
When the mirror port was specified on the switch, untagged ports would
start to transmit tagged traffic.
This issue has been resolved.
CR00013178
Switch
2
In packet storm conditions, involving a high percentage of routing
protocol packets, the switch could become very low on resources, and
reboot.
This issue has been resolved.
CR00013275
Firewall
2
If a firewall policy had a list attached to it (by using the command
add
firewall policy=
policy-name
list=
list-name
), destroying the policy
would cause the switch to reboot.
This issue has been resolved.
CR00013380
IP Gateway
2
In certain unusual network configurations, the switch would respond to
ICMP messages addressed to it with the wrong source IP address in the
reply.
This issue has been resolved.
CR00013598
IP Gateway
2
If the switch had multiple default routes with the same nexthop (such as
one static default route and a default route learnt by RIP) and one of those
default routes was withdrawn, then the hardware entry for the default
route would be removed. This meant that traffic destined to that route
was forwarded to the CPU, which could result in a performance
degradation.
This issue has been resolved.
CR00014044
IGMP
2
When large numbers of multicast streams were passing through the
switch and there was no multicast routing protocol running (such as PIM
or DVMRP), the CPU would experience regular periods of extended high
utilisation. This could result in lost control packets and network instability.
This issue has been resolved.
CR
Module
Level
Description
