Cisco Cisco IOS Software Release 12.2(33)SRE

Page de 106
1403
Caveats for Cisco IOS Release 12.2(33)SRA through 12.2(33)SRA7
OL-10394-05 Rev. R0
IP Routing Protocols
CSCei93982
Symptoms: A router that is configured for NAT may crash.
Conditions: This symptom is observed when an application uses two well-known ports: one for the 
source and the other for the destination. After the outgoing translation is created, on return, when 
the previous source port is used as the destination, NAT may use an incorrect algorithm.
For example, when a PPTP session is initiated to well-known port 1723 from source port 21 (FTP), 
then the outgoing packet creates a FTP translation. (Look at the source information when going from 
in to out). When the packet is returned, look again at the source information to see what kind of 
packet is returned. In this situation, with source port 1723, NAT assumes that the packet is a PPTP 
packet, and then attempts to perform PPTP NAT operations on a data structure that NAT has built 
for a FT P packet, causing the router to crash.
Workaround: There is no workaround. 
CSCej20707
Symptoms: The CPU usage may be high, and an IGP (OSPF or IS-IS) adjacency may drop when 
PIM sparse mode (PIM-SM) stress traffic is being processed.
Conditions: This symptom is observed on a Cisco router that connects to a receiver and that has 
60,000 (s,G) join messages. The symptom occurs when you enter the show ip mroute count 
command or when there is an abrupt increase in multicast groups.
Workaround: Do not enter the show ip mroute count command. Rather, enter the show ip mroute 
count terse
 command. Increase multicast groups gradually to avoid high CPU usage. In addition, 
the following actions may also help to alleviate the symptoms:
Enter the ip pim register-rate-limit command on the first hop.
Enter the ip pim fast-register-stop on the PIM-RP.
Disable RP rate-limiting commands on the PIM-RP and first hop. 
CSCsb96034
Symptoms: Routes redistributed from other routing protocols to BGP will be deleted and re-added 
after an NSF switchover, potentially causing traffic to go down for a long period of time.
Conditions: This symptom may occur when the route is redistributed from other routing protocols 
(such as OSPF, ISIS, EIGRP) to BGP.
Workaround: There is no workaround. 
CSCsd63038
Symptoms: An MDT address-family session in a BGP environment may not come up between two 
PE routers. This situation prevents the tunnel interface from being shown in the output of the show 
ip pim vrf
 vrf-name neighbor command on one of the PE routers.
Conditions: This symptom is observed on PE routers that are configured for Multicast VPN and that 
have the following commands enabled:
address-family ipv4 mdt
neighbor neighbor-ip-address activate neighbor
neighbor neighbor-ip-address send-community extended
Workaround: Reconfigure the address-family ipv4 mdt command in the BGP environment.