Cisco Cisco IOS Software Release 12.4(4)T
1417
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(2)T2
•
CSCsb59813
Symptoms: The H323-SIP gateway rejects valid SUBSCRIBEs with a '481 Call Leg/Transaction
Does Not Exist' response message. The gateway may also crash.
Does Not Exist' response message. The gateway may also crash.
Conditions: This symptom has been observed after the gateway receives an INVITE with Replaces
header for a call that has an active subscription, and then subsequent SUBSCRIBE requests are
received for that call.
header for a call that has an active subscription, and then subsequent SUBSCRIBE requests are
received for that call.
Workaround: There is no workaround.
•
CSCsb69726
Symptoms: Cisco IOS Client could not understand the back server list if it has more than one back
server pushed by the Cisco VPN 3000 Concentrator.
server pushed by the Cisco VPN 3000 Concentrator.
Conditions: This symptom has been observed on all releases supporting back server feature and is
applicable only for Cisco VPN 3000 Concentrator with Cisco IOS Client.
applicable only for Cisco VPN 3000 Concentrator with Cisco IOS Client.
Workaround: Do not add more than one backup server to the client group configuration of the
Cisco VPN 3000 Concentrator.
Cisco VPN 3000 Concentrator.
Further Problem Description: As per the Unity Client protocol during the mode configuration reply,
the back server list pushed by the concentrator can be delimited by " ,\r\n|". Since the Cisco IOS
Client does not understand the " " space delimiter sent by the Cisco VPN 3000 Concentrator, the
Cisco IOS Client misunderstands the entire back up server list as a single backup server.
the back server list pushed by the concentrator can be delimited by " ,\r\n|". Since the Cisco IOS
Client does not understand the " " space delimiter sent by the Cisco VPN 3000 Concentrator, the
Cisco IOS Client misunderstands the entire back up server list as a single backup server.
•
CSCsb84615
Symptoms: The error message appears on a Cisco 1812 router during high traffic load.
*Sep 9 04:54:38.468: %MOTCR-3-CMD_ERR: MOTCR command returned error: (0x1048)
*Sep 9 04:54:38.468: motcr_lopri_error: unknown error 0x1048
*Sep 9 04:54:38.468: IPSECcard: an error coming back 0x1048
*Sep 9 04:54:38.688: %MOTCR-3-CMD_ERR: MOTCR command returned error: (0x1048)
*Sep 9 04:54:38.688: motcr_lopri_error: unknown error 0x1048
*Sep 9 04:54:38.688: IPSECcard: an error coming back 0x1048
*Sep 9 04:54:38.912: %MOTCR-3-CMD_ERR: MOTCR command returned error: (0x1048)
*Sep 9 04:54:38.912: motcr_lopri_error: unknown error 0x1048
*Sep 9 04:54:38.912: IPSECcard: an error coming back 0x1048
Conditions: This symptom has been observed on Cisco 180x and Cisco 181x routers with Cisco IOS
Release 12.4(2)T, Release 12.4(2)T1, Release 12.4(2)YI, Release 12.4(2)YT, and
Release 12.4(2)XA and with the k9 images.
Release 12.4(2)T, Release 12.4(2)T1, Release 12.4(2)YI, Release 12.4(2)YT, and
Release 12.4(2)XA and with the k9 images.
Workaround: There is no workaround.
•
CSCsb85920
Symptoms: The default route is added on the EzVPN server.
Conditions: When the inside interface has no IP address assigned or the cascaded ACL has the ip
any any command, a default route gets pushed to the server which the server adds without
validating.
any any command, a default route gets pushed to the server which the server adds without
validating.
Workaround: Ensure the inside interface has an IP address. Do not add the ip any any command to
a cascaded network access-list.
a cascaded network access-list.
•
CSCsb85927
Symptoms: Previous routes on the EzVPN server are not deleted when the EzVPN client reconnects.