Filter
Top Products
6 Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
When IP filters are configured on IP interfaces of the switch, all IP routing
must occur in software. To achieve this, the IP forwarding table in the ASIC
must be emptied. There was an issue whereby Interim IP route entries (IP
routes for which there is not yet an ARP entry for the nexthop address) were
not removed from the hardware IP forwarding table when an IP filter was
added to an IP interface. This issue has been resolved.
If the switch received many packets to Layer 3 route, but did not have ARP
entries for the destination address, the switch memory would deplete,
leading to a switch reboot. This issue has been resolved.
For OSPF-originated routes, it was possible for a route to be deleted from
the IP routing table, but still be referenced by OSPF. This could cause a
switch reboot when later generating a summary LSA that contained the old
route. This occurred using the reset ip command. This issue has been
resolved.
If the configuration script on the switch contained several commands for
creating static arp entries, the switch could reboot on startup. This issue has
been resolved.
A memory leak could occur when the accessing of the environmental
monitoring chip failed. This issue has been resolved.
When a BGP peer was physically disconnected, the best routes for all
prefixes learned were written to the silicon. The memory that was used to
contain these routes was sometimes not freed, resulting in a memory leak.
This issue has been resolved.
When DHCP is enabled, it reclaims IP addresses at switch startup to
determine if the addresses are in use or not. If, during this process, DHCP
was disabled then re-enabled, the switch would not attempt to reclaim the
remaining IP address ranges. This would lead to the rejection of DHCP
requests for IP addresses that were still being reclaimed. This issue has been
resolved.
When doing AS-Path regular expression matching in the show bgp route
command, the router could reboot if there were withdrawn routes in the
BGP table. This issue has been resolved.
PCR: 40473 Module: IPG Level: 2
PCR: 40478 Module: IPG Level: 2
PCR: 40479 Module: OSPF Level: 2
PCR: 40481 Module: IPG Level: 2
PCR: 40487 Module: CORE Level: 2
PCR: 40488 Module: IPG Level: 2
PCR: 40496 Module: DHCP Level: 2
PCR: 40500 Module: BGP Level: 2