Cisco Cisco IOS Software Release 12.4(4)T

ページ / 302
1121
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
  Resolved Caveats—Cisco IOS Release 12.4(9)T3
CSCsi04183
Symptoms: A router that is configured as an EasyVPN client is not able to auto connect to the 
EasyVPN server using its saved Xauth username/password.
Conditions: This symptom is observed when the router is powered-up or when the ISAKMP 
re-keying happens.
Workaround: Manually execute the crypto ipsec client ezvpn xauth command in the router console 
and enter the respective username/password. 
TCP/IP Host-Mode Services
CSCse05736
Symptoms: A router that is running RCP can be reloaded by a specific packet.
Conditions: This symptom is seen under the following conditions:
The router must have RCP enabled.
The packet must come from the source address of the designated system configured to send RCP 
packets to the router.
The packet must have a specific data content.
Workaround: Put access lists on the edge of your network blocking RCP packets to prevent spoofed 
RSH packets. Use another protocol such as SCP. Use VTY ACLs. 
CSCsg00102
Symptoms: In Cisco IOS Release 12.4(9)T, the TCP stops accepting new connections after a few 
days of SSLVPN running in the router. The debug ip tcp transaction command shows the error with 
connection queue limit reached. When the problem happens, the show tcp bri all command shows 
five connections in CLOSED state.
Conditions: This symptom is observed in Cisco IOS Release 12.4(9)T.
Workaround: Enter the clear tcp tcb * command. This command will clear all the TCP connections 
on the router. 
Wide-Area Networking
CSCek41260
Symptoms: The router crashes while it receives an incoming pad call through the TTY line.
Conditions: This symptom has been observed only when the pad call comes through the TTY line, 
but not when it comes through the serial interface.
Workaround: There is no workaround. 
CSCek59078
Symptoms: An L2TPv3 session is established when voluntary tunneling is configured and both peers 
have corresponding configurations. However, after you configure a pseudowire on a virtual PPP 
interface on one of the peers, the session on this peer is up but the line protocol is down, an a 
“virtual-PPP1 is up, line protocol is down” error message is generated.
Conditions: This symptom is observed when the virtual PPP interface is first deleted via the no 
interface virtual-ppp
 number command and then reconfigured via the interface virtual-ppp 
number command before you configure a pseudowire on the virtual PPP interface.