Cisco Cisco IOS Software Release 12.0 S Release Notes

Page of 500
1653
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
  
Resolved Caveats—Cisco IOS Release 12.0(25)S2
Symptoms: A Cisco router may reload when you add Border Gateway Protocol (BGP) neighbor 
statements to the configuration.
Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0) S or 
Release 12.2 S when BGP neighbors are added by using a script that adds the BGP neighbors at a 
much faster rate than manual addition, and when a large BGP table is already present on the router 
before the script adds the BGP neighbors.
Workaround: There is no workaround.
CSCeb17467
Symptoms: A Cisco router may reload when Border Gateway Protocol (BGP) is configured to carry 
Virtual Private Network version 4 (VPNv4) routes.
Conditions: This symptom is observed when VPNv4 import processing occurs simultaneously with 
a BGP neighbor reset, for example, when a VPN routing and forwarding (VRF) instance is 
configured and you enter the clear ip bgp * privileged EXEC command.
Workaround: There is no workaround. 
CSCeb30370
Symptoms: A Cisco 12000 series may reload because of a race condition when you enter the no 
router ospf
 global configuration command or the no ip vrf global configuration or router 
configuration command.
Conditions: This symptom is observed when you run a configuration script in which the commands 
are entered in a very fast sequence.
Workaround: There is no workaround. 
CSCeb57086
Symptoms: A Cisco 10000 series that is configured with two Performance Routing Engine 1 
(PRE-1) processors may stop functioning as a redundant system.
Conditions: This symptom is observed when you enter the bgp upgrade-cli router configuration 
command.
Workaround: Reload the standby PRE-1. 
CSCeb63120
Symptoms: When refresh reduction is enabled and a Cisco router has been operational for a long 
time, valid Resource Reservation Protocol (RSVP) messages that are received from a neighbor may 
be dropped when the message IDs have cycled through the entire number space once (that is, from 
0 to 4,294,967,295) and then progressed up to 2,147,483,648 (0x80000000).
Conditions: This symptom is observed when a message ID number space begins at zero, increases 
up to 4,294,967,295 (32 bits), but then does not properly wrap back to zero, causing message IDs 
greater than 2,147,483,648 to be out of sequence, and to be dropped.
Note that a neighboring router is able to send Message IDs and properly wraps back from 
4,294,967,295 to zero, but the receiving router that does not record the wrap event, causing the 
symptom to occur.
Workaround: There is no workaround. 
CSCeb85136
Symptoms: An IP packet that is sent with an invalid IP checksum may not be dropped.