Cisco Cisco IOS Software Release 12.4(23)
908
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
Resolved Caveats—Cisco IOS Release 12.4(1b)
Conditions: This symptom is observed when the network network-number command is enabled to
introduce connected networks into a BGP topology and when, afterwards, BGP is redistributed into
IS-IS. The symptom occurs after one of the interfaces that forms a network connection goes down
and comes up again; the network re-enters the BGP topology but is no longer redistributed into
IS-IS.
introduce connected networks into a BGP topology and when, afterwards, BGP is redistributed into
IS-IS. The symptom occurs after one of the interfaces that forms a network connection goes down
and comes up again; the network re-enters the BGP topology but is no longer redistributed into
IS-IS.
Workaround: There is no workaround.
•
CSCsa87473
Symptoms: A BGP speaker may fail to send all of its prefixes to a neighbor if the neighbor sends a
refresh request to the BGP speaker at the same time that the BGP speaker is generating updates to
the neighbor. This situation causes the neighbor to miss some prefixes from its BGP table.
refresh request to the BGP speaker at the same time that the BGP speaker is generating updates to
the neighbor. This situation causes the neighbor to miss some prefixes from its BGP table.
Conditions: This symptom may occur between any pair of BGP speakers.
A common scenario is that a VPNv4 PE router is reloaded and then fails to learn all prefixes from
its route reflector (RR). In this configuration, the symptom occurs when the processing of a VRF
configuration causes the PE router to automatically generate a route-refresh request to the RR, while
the RR is still generating updates to the PE.
its route reflector (RR). In this configuration, the symptom occurs when the processing of a VRF
configuration causes the PE router to automatically generate a route-refresh request to the RR, while
the RR is still generating updates to the PE.
Workaround: There is no workaround.
•
CSCsa94774
Symptoms: When you enter the traceroute command from an IP address that is different from the
address in the NAT default configuration, the incoming PAT sends the reply packets to the NAT
default address that is defined in the NAT default configuration and not to the original source address
from which the traceroute command was entered. Note that the outside PAT works fine.
address in the NAT default configuration, the incoming PAT sends the reply packets to the NAT
default address that is defined in the NAT default configuration and not to the original source address
from which the traceroute command was entered. Note that the outside PAT works fine.
Conditions: This symptom is platform-independent. NAT overload traffic and other TCP traffic is
not affected.
not affected.
Workaround: There is no workaround.
•
CSCsa98059
Symptoms: Suboptimal routing occurs in an OSPF configuration or a routing loop occurs between
two border routers that redistribute BGP into OSPF.
two border routers that redistribute BGP into OSPF.
Conditions: These symptoms are observed when at least two border routers are connected via eBGP
to another autonomous system, receive the same prefix over these connections, and redistribute the
prefix into OSPF. Under certain conditions, for example when the eBGP session from the preferred
BGP exit point to the eBGP peer flaps, the second router in the local autonomous system becomes
the preferred path and redistributes the eBGP route into OSPF. When the eBGP session with the first
router comes back up, the LSA should be flushed but this does not occur. This situation may create
routing problems on other OSPF routers or, when BGP has a higher administrative distance than
OSPF, routing loops between both border routers.
to another autonomous system, receive the same prefix over these connections, and redistribute the
prefix into OSPF. Under certain conditions, for example when the eBGP session from the preferred
BGP exit point to the eBGP peer flaps, the second router in the local autonomous system becomes
the preferred path and redistributes the eBGP route into OSPF. When the eBGP session with the first
router comes back up, the LSA should be flushed but this does not occur. This situation may create
routing problems on other OSPF routers or, when BGP has a higher administrative distance than
OSPF, routing loops between both border routers.
Workaround: There is no workaround.
•
CSCsb07372
Symptoms: NAT H.323 does not create an entry in the NAT translation table even though debugging
shows that NAT processes the packet correctly. This situation causes one-way voice for the called
party, preventing them from hearing the calling party.
shows that NAT processes the packet correctly. This situation causes one-way voice for the called
party, preventing them from hearing the calling party.
Conditions: This symptom is observed only when ICMP error messages are processed by NAT.
Workaround: There is no workaround.
•
CSCsb13988
Symptoms: A router that is configured for NAT may crash because of a bus error.