Cisco Cisco IOS Software Release 12.4(23)
773
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
Resolved Caveats—Cisco IOS Release 12.4(5)
Conditions: This symptom is observed on a Cisco 7200 series that runs Cisco IOS interim
Release 12.4(3.9)T1 when the ip cef command is enabled. The symptom may also affect other
platforms and may also occur in Release 12.4.
Release 12.4(3.9)T1 when the ip cef command is enabled. The symptom may also affect other
platforms and may also occur in Release 12.4.
Workaround: Do not enter the debug vpdn packet command.
First Alternate Workaround: Disable CEF by entering the no ip cef command before you enter the
debug vpdn packet command. When the debug output is generated, re-enable CEF by entering the
ip cef command.
debug vpdn packet command. When the debug output is generated, re-enable CEF by entering the
ip cef command.
Second Alternate Workaround: When traffic has started to flow, enter the show vpdn command
before you enter the debug vpdn packet command.
before you enter the debug vpdn packet command.
•
CSCej45061
Symptoms: Attempts to remove a PRI group fail.
Conditions: This symptom is observed when an NFAS group has group number 0 and when you
attempt to remove a FAS PRI group.
attempt to remove a FAS PRI group.
Workaround: Shut down the NFAS group before you remove the FAS PRI group.
•
CSCin92814
Symptoms: A router crashes when you enter the no ip vrf vrf-name global configuration command.
Conditions: This symptom is observed only when you remove the VRF configuration immediately
after removing VRF forwarding from an interface.
after removing VRF forwarding from an interface.
Workaround: Wait for 60 seconds between removing VRF forwarding from the interface and
removing the VRF configuration.
removing the VRF configuration.
•
CSCsa42221
Symptoms: A call reference flag is missing from a TBCT request message to a third-party vendor
ISDN switch.
ISDN switch.
Conditions: This symptom is observed on a Cisco AS5400 but may also occur on other platforms.
Workaround: There is no workaround.
•
CSCsa55747
Symptoms: The RADIUS L2TP-specific disconnect code value for the Ascend-Disconnect-Cause
RADIUS attribute (195) is incorrectly generated as 607 instead of 605.
RADIUS attribute (195) is incorrectly generated as 607 instead of 605.
Conditions: This symptom is observed when an L2TP tunnel setup failure occurs between a LAC
and an LNS.
and an LNS.
Workaround: There is no workaround.
•
CSCsa73159
Symptoms: No final billing record is made for a call.
Conditions: This symptom is observed when a call is made using a Two B-Channel Transfer (TBCT)
TCL script in the following scenario:
TCL script in the following scenario:
–
The Telco switch signals the TBCT call with a special FACILITY message.
–
A call leg is created between point A and point B, and another call leg is created between
point C and point D.
point C and point D.
–
TBCT connects point A to point D to release the TDM resources.
–
A billing start record is made for each call leg.
–
When the final call between point A and point D is released and a NOTIFY message is received,
no final billing record is made for this call.
no final billing record is made for this call.