Cisco Cisco IOS Software Release 12.4(4)T
1189
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(6)T9
40C3BA10 40C3CCE0CMD: 'end'
%SYS-5-CONFIG_I: Configured from console by console
%SYS-2-CHUNKBADMAGIC: Bad magic number in chunk header,
chunk 45519C14 data 4552953C chunkmagic 15A3C78B chunk_freemagic 0
-Process= "Check heaps", ipl= 0, pid= 6
-Traceback= 4063C5FC 4063C788 4065A9D0
chunk_diagnose, code = 2
chunk name is IP RDB Chunk
current chunk header = 0x0x4552952C
data check, ptr = 0x0x4552953C
next chunk header = 0x0x4552957C
data check, ptr = 0x0x4552958C
previous chunk header = 0x0x455294DC
data check, ptr = 0x0x455294EC
Conditions: This symptom is observed mostly with configuration changes that involve the bgp
dmzlink-bw command for a BGP IPv4 address family, but in very rare cases, the symptom may also
occur on other situations.
dmzlink-bw command for a BGP IPv4 address family, but in very rare cases, the symptom may also
occur on other situations.
Workaround: There is no workaround.
•
CSCsg55591
Symptoms: When there are link flaps in the network, various PE routers receive the following error
message:
message:
%BGP-3-INVALID_MPLS: Invalid MPLS label (1) received in update for prefix
155:14344:10.150.3.22/32 from 10.2.2.1
Or, a local label is not programmed into the forwarding table for a sourced BGP VPNv4 network.
Conditions: These symptoms are observed when an iBGP path for a VPNv4 BGP network is present,
and then a sourced path for the same route distinguisher (RD) and prefix is brought up.
and then a sourced path for the same route distinguisher (RD) and prefix is brought up.
Workaround: Remove the iBGP path. Note that when the sourced path comes up first, the symptoms
do not occur.
do not occur.
Alternate Workaround: Use different RDs with the different PE routers. When the RD and prefix do
not match exactly between the iBGP path and the sourced path, the symptoms do not occur.
not match exactly between the iBGP path and the sourced path, the symptoms do not occur.
•
CSCsj10772
Symptoms: The TTL of a CNAME will be zeroed on a DNS reply after passing through a
Cisco router that is configured for Network Address Translation (NAT).
Cisco router that is configured for Network Address Translation (NAT).
Conditions: This symptom is observed on a Cisco router that is configured for NAT that is running
Cisco IOS Release 12.4 or 12.4T. Only CNAME records are affected.
Cisco IOS Release 12.4 or 12.4T. Only CNAME records are affected.
Workaround: Use static NAT translations with the keyword “no-payload”.
•
CSCsj39538
Symptoms: Router tracebacks and then crashes during deconfiguration (removal) of VRF. The
following message was seen prior to crash:
following message was seen prior to crash: