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

CSCsc02825

Symptoms: In Cisco IOS software that is running the Multiprotocol Label Switching (MPLS) Label 
Distribution Protocol (LDP), the router could reload while trying to access a bad virtual address.

Conditions: This symptom may be observed when LDP is being used. It will not be observed with 
TDP. It may happen when LDP receives a protocol message larger than 512 bytes right after 
receiving several Label Mapping messages smaller than 25 bytes. This problem is likely to be 
accompanied by the presence of one of the following error message:

Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0xD0D0D0D

The above error message may be preceded by one of the following four error messages:

%ALIGN-1-FATAL: Corrupted program counter 19:45:07 CET Mon Sep 26 2005

    pc=0xD0D0D0D, ra=0x61164128, sp=0x64879B98

%TDP-3-BAD_PIE: peer x.x.x.x; unknown pie type 0x11E

%TDP-3-UNEXPECTED_PIE: peer x.x.x.x unexpected pie type 0x0

%TDP-3-PTCLREAD: peer x.xx.x0, read failure

This problem may be seen in releases that include the fix for CSCeg74562 but do not have the fix 
associated with this defect.

Workaround: There is no workaround. 

CSCeh35980

Symptoms: A router may reload in a TCP function.

Conditions: This symptom is observed in a complex scenario with a large number of BGP peers 
when neighbors are shut down and brought up again.

Workaround: There is no workaround. 

CSCee85138

Symptoms: A SegV exception crash may occur on a Cisco router that is configured for voice calls.

Conditions: This symptom is observed on a Cisco 2600 series that runs Cisco IOS Release 12.3(6a) 
or Release 12.3(9) but may not be platform-dependent.

Workaround: There is no workaround. 

CSCeg20283

Symptoms: E1R2 SS7 calls fail to come up when more than one call is made with the following 
ISDN error:

ISDN Se1/6:15 SC **ERROR**: call_connect: call_id not found, rejecting call

ISDN **ERROR**: Module-CCPRI Function-CCPCC_CallConnected Error-Unknown event 

received in message from L3 or Host: 4F

Conditions: This symptom is observed on a Cisco platform that runs Cisco IOS Release 12.3(11)T.

Workaround: There is no workaround.