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

Descargar
Página de 302
1096
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
  Resolved Caveats—Cisco IOS Release 12.4(9)T4
gateway (OGW) is configured for the National ISDN (primary-ni) switch type, and when the TGW 
is c onfigured for the NT DMS-100 (primary-dms100) switch type. The symptom may also affect 
Release 12.4T.
Workaround: There is no workaround. 
Resolved Caveats—Cisco IOS Release 12.4(9)T4
Cisco IOS Release 12.4(9)T4 is a rebuild release for Cisco IOS Release 12.4(9)T. The caveats in this 
section are resolved in Cisco IOS Release 12.4(9)T4 but may be open in previous Cisco IOS releases. 
The following information is provided for each caveat:
Symptoms—A description of what is observed when the caveat occurs.
Conditions—The conditions under which the caveat has been known to occur.
Workaround—Solutions, if available, to counteract the caveat.
Basic System Services
CSCsd58772
Symptoms: The MIB object rttMonLatestRttOperTime returns a value of 0.
Conditions: This symptom occurs for IPSLA RTP operation only irrespective of whether the 
operation succeeds or fails. 
Workaround: There is no workaround. 
CSCsh85879
Symptoms: A router crashes while executing the type slm frame-relay interface command. 
Conditions: This symptom has been observed with a Cisco 7200 router loaded with Cisco IOS 
interim Release 12.4(13.2)T. 
Workaround: There is no workaround. 
IP Routing Protocols
CSCsh02161
Symptoms: A Route Reflector (RR) does not withdraw a prefix that redistributes itself even if this 
prefix is removed from the BGP table.
Condition: This symptom is observed on a Cisco router that functions as an RR that advertises two 
of the same prefixes with different Route Distinguishers (RDs) when one of these prefixes 
redistributes itself and when the other prefix is a route that is learned from an RR client via iBGP.
Workaround: There is no workaround. 
CSCsh84102
Symptoms: These symptoms have been observed:
Some DMVPN spokes may become unreachable and a loop will appear in a traceroute.
The adjacency rewrite information, when looking from the hub in the show adjacency details 
command, for a problematic spoke will be the same as for another spoke.