Cisco Cisco IOS Software Release 12.4(4)T

Conditions: This symptom is observed on a Cisco router and is most likely to occur when a large 
number of type 3, type 5, or type 7 LSAs are advertised and withdrawn.

Workaround: Trigger an action that causes a full SPF computation. 

CSCsc33408

Symptoms: The router reloads unexpectedly when unconfiguring the static route.

Conditions: Remove the static route which was configured and then unconfigured from the BGP and 
IPv4 multicast address-family. The crash has been observed when the static route was unconfigured 
after clearing the bgp routes.

Workaround: There is no workaround.

CSCsc59089

Symptoms: BGP does not advertise all routes to a peer that sends a route-refresh request.

Conditions: This symptom is observed under the following conditions:

The router is in the process of converging all of its peers and has updates ready in the output 
queue for the peer.

The peer sends a route-refresh request to the router. This may occur when the clear ip bgp * 
soft in command is entered on the peer or when a VRF is added to the peer.

The router processes the route-refresh request from the peer while the router still has updates in 
the output queue for the peer.

In this situation, all of prefixes that are advertised by the unsent updates in the output queue for the 
peer are lost.

Workaround: There is no workaround. When the symptom has occurred, enter the clear ip bgp * 
soft out command on the router to force the router to send all updates to its peers. 

CSCsc78813

Symptoms: While using NAT in an overlapping network configuration, the IP address inside a DNS 
reply payload from the nameserver is not getting translated at the NAT BOX.

Conditions: The above symptom is seen in Cisco routers that are loaded with Cisco IOS 
Release 12.3(18) image, configured with the ip nat outside source command.

Workaround: There is no workaround. 

CSCed28266

Symptoms: A Cisco gateway may unexpectedly reload because of a software-forced crash when it 
builds a SIP ACK(nowledgement) or BYE message.

Conditions: This symptom is observed when the gateway receives a SIP response that contains a 
Record-Route header and a Contact header and when the length of the Contact header exceeds 
128*n, in which "n" is the number of URLs in the Record-route header.

Workaround: There is no workaround.