Cisco Cisco IOS Software Release 12.4(4)T
1047
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(11)T1
•
CSCsi28578
Symptoms: When an LNS renegotiates LCP with a client, a LAC may not forward a CONFREQ
message from the client to the LNS. This situation may cause a loop with LCP negotiation and
authentication between the client and the LNS, and an L2TP tunnel is established between the LAC
and the LNS.
message from the client to the LNS. This situation may cause a loop with LCP negotiation and
authentication between the client and the LNS, and an L2TP tunnel is established between the LAC
and the LNS.
Conditions: This symptom is observed when the debug snmp packet is enabled and when the
following configurations are present:
following configurations are present:
On the LNS, the lcp renegotiation always command is enabled:
vpdn-group <vpdn group name>
lcp renegotiation always
On the LAC, the snmp-server trap for l2tun session command is enabled:
snmp-server enable traps l2tun session
snmp-server host <IP-address> version 2c <community>
Workaround: Do no enable the debug snmp packet command when the lcp renegotiation always
command is enabled on the LSN and when the snmp-server trap for l2tun session command is
enabled on the LAC.
command is enabled on the LSN and when the snmp-server trap for l2tun session command is
enabled on the LAC.
Resolved Caveats—Cisco IOS Release 12.4(11)T1
Cisco IOS Release 12.4(11)T1 is a rebuild release for Cisco IOS Release 12.4(11)T. The caveats in this
section are resolved in Cisco IOS Release 12.4(11)T1 but may be open in previous Cisco IOS releases.
section are resolved in Cisco IOS Release 12.4(11)T1 but may be open in previous Cisco IOS releases.
The following information is provided for each caveat:
•
Symptoms—A description of what is observed when the caveat occurs.
•
Conditions—The conditions under which the caveat has been known to occur.
•
Workaround—Solutions, if available, to counteract the caveat.
IP Routing Protocols
•
CSCsg84972
Symptoms: After upgrading to Cisco IOS Release 12.4(11)T, tunnel protection shared stopped
working for additional tunnels between 2 peers.
working for additional tunnels between 2 peers.
Conditions: This symptom has been observed with DMVPN - 2 peers with multiple tunnels (each
tunnel is decapsulated in a different VRF. Each tunnel is a distinct DMVPN network.
tunnel is decapsulated in a different VRF. Each tunnel is a distinct DMVPN network.
Tunnel protection [shared] is used since Spoke tunnel source is located in global vrf and uses
Loopback1. The tunnel destination is the hub (loopback1).
Loopback1. The tunnel destination is the hub (loopback1).
R103 ([loopback0] is the destination for all tunnels sourced from R100SP loopback 0 [10.1.1.1]
Workaround: There is no workaround.