Cisco Cisco IOS Software Release 12.4(23) Notas de publicación

Descargar
Página de 610
529
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
  Resolved Caveats—Cisco IOS Release 12.4(8)
no ip nat pool 
name
Workaround: There is no workaround. 
CSCsd64173
Symptoms: A router may reload unexpectedly because of a bus error crash after you have removed 
summary-prefix IPv6 OSPF command.
Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.2(18)SXF 
but may also occur in other releases. The symptom occurs only when the summary-prefix IPv6 
OSPF command is configured without any redistribute commands.
Workaround: Configure a redistribute command under the IPv6 OSPF configuration. 
CSCsd67591
Symptoms: A router may crash when you modify parameters of the route-map command for a 
redistribution statement.
Conditions: This symptom is observed when you modify the parameters of the route-map command 
for a redistribution statement of an OSPF process that was deleted.
Workaround: Delete the redistribution statement before you delete the OSPF process. 
CSCsd84489
Symptoms: A platform that is configured for Open Shortest Path First (OSPF) and incremental 
Shortest Path First (SPF) may crash when changes occur in the OSPF topology.
Conditions: This symptom is observed on a Cisco platform that has the ispf command enabled when 
changes occur in the OSPF topology that cause the intra-area routes to be updated.
Workaround: Disable the ispf command. 
CSCuk58462
Symptoms: When a route map is configured, routes may not be filtered as you would expect them 
to be filtered.
Conditions: This symptom is observed on a Cisco router that is configured for BGP and that 
functions in an MPLS VPN environment.
Workaround: There is no workaround.
Further Problem Description: The symptom does not occur for redistributed route maps. 
ISO CLNS
CSCsb89900
This caveat consists of two symptoms, two conditions, and two workarounds:
1.
Symptom 1: Corrupted timer data structures may cause tracebacks in an IS-IS environment.
Condition 1: This symptom is observed when an IS-IS instance is configured for IPv6 interfaces 
only, when the IS-IS instance has a passive interface, and when you take the following actions:
– You enter the no router isis command.
– You then re-enable IS-IS, including on the passive interface, which then becomes an active
IPv6 interface.