Cisco Cisco IOS Software Release 12.4(23)

Page de 610
443
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
  Resolved Caveats—Cisco IOS Release 12.4(10)
CSCsf03251
Symptoms: Primary and backup NFAS interfaces may transition from WAIT to OOS even after 
receiving “in-service” message from the PSTN.
Conditions: This symptom is observed on a Cisco AS5400XM that is running several Cisco IOS 
12.4 mainline and 12.4T releases.
Workaround: There is no workaround. 
Resolved Caveats—Cisco IOS Release 12.4(10)
This section describes possibly unexpected behavior by Cisco IOS Release 12.4(10). All the caveats 
listed in this section are resolved in Cisco IOS Release 12.4(10). This section describes severity 1 and 2 
caveats and select severity 3 caveats.
Basic System Services
CSCek33076
Symptoms: A RADIUS progress code is incorrectly reported for a call that fails at IPCP. The 
progress code reports that the Link Control Protocol (LCP) is the open state.
Conditions: This symptom is observed on a Cisco platform that runs Cisco IOS Release 12.4(3a) 
and that is configured for AAA.
Workaround: There is no workaround. 
CSCek37174
Symptoms: When you configure RADIUS servers via the AAA-SERVER-MIB, the expected 
behavior is that the last defined RADIUS server receives the lowest priority, but this does not occur.
Conditions: This symptom is observed on a Cisco router that is configured for AAA and that runs 
Cisco IOS Release 12.4 or Release 12.4T.
Workaround: There is no workaround. 
CSCek40060
Symptoms: RADIUS server authentication may not function for dialup and PPP clients.
Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.4(7) and 
that has the radius-server retry method round-robin command enabled.
Workaround: Disable the radius-server retry method round-robin command. Note that the 
symptom does not occur in Release 12.3 or Release 12.3T. 
CSCin99788
Symptoms: An %AAA-3-ACCT_LOW_MEM_TRASH error message is generated when a 
low-memory condition occurs. When this situation occurs, a memory leak may occur in AAA data.
Conditions: This symptom is observed when an interface flaps and causes a very large number of 
sessions to go down simultaneously, in turn generating a very large number of accounting stop 
records. In this situation, the I/O memory may be held for a long time when accounting records are 
send and when an AAA server is slow or unreachable.
Workaround: There is no workaround.