Cisco Cisco IOS Software Release 12.2
105
Caveats for Cisco IOS Release 12.2
OL-3513-16 Rev. G0
Resolved Caveats—Cisco IOS Release 12.2(24a)
•
CSCee49862
Symptoms: A Cisco 7500 series multichannel T3 port adapter (PA-MC-2T3+) may not provide a
two-second delay before bringing down the T3 controller.
two-second delay before bringing down the T3 controller.
Conditions: This symptom is observed when an alarm as defined in the ANSI T1.231 specification
occurs.
occurs.
Workaround: There is no workaround.
•
CSCee61646
Symptoms: A multicast packet is not correctly encrypted through IPSec and GRE.
Conditions: This symptom is observed when PIM announcement packets are distributed through
tunnels and when the crypto map that specifies the protection on the GRE traffic is only applied to
the physical interface. Even though this is a correct way to apply the crypto map only to the physical
interface to protect the GRE traffic, crypto policy checking is missing on PIM announcement
packets.
tunnels and when the crypto map that specifies the protection on the GRE traffic is only applied to
the physical interface. Even though this is a correct way to apply the crypto map only to the physical
interface to protect the GRE traffic, crypto policy checking is missing on PIM announcement
packets.
Workaround: Apply the crypto map to both the tunnel interface and the physical interface.
•
CSCin75294
Symptoms: The show controller T3 command does not show T1 level alarm history. Alarm history
is not maintained at T1 level.
is not maintained at T1 level.
Conditions: This symptom is observed on Cisco 7500 series routers.
Workaround: There is no workaround.
TCP/IP Host-Mode Services
•
CSCec66723
Symptoms: Cisco IOS TCP backs off for second packet in retransmission Queue.
Conditions: When the TCP stack has couple packets in the retransmission queue, it means that these
packets were either dropped in the network or were not reliably received by the remote end. Under
this condition, TCP goes into slow start, sends the first packet in the retransmission queue and backs
off the retransmission timer. This repeated till we get an ACK for the packet. No other packet in the
retransmission queue is sent unless we get the ACK for the earlier packet in the retransmission
queue. When the ACK comes in, TCP is supposed to retain the same krtt values for sending the next
packet in the queue. However, IOS TCP backs off yet again, causing a slightly slower sending of
packets in the retransmission queue. The impact of this is supposed to be minimal. Once the packets
in the retransmit queue are cleared (ACKed), TCP will return to its old state of sending data up to
the window advertised by the peer.
packets were either dropped in the network or were not reliably received by the remote end. Under
this condition, TCP goes into slow start, sends the first packet in the retransmission queue and backs
off the retransmission timer. This repeated till we get an ACK for the packet. No other packet in the
retransmission queue is sent unless we get the ACK for the earlier packet in the retransmission
queue. When the ACK comes in, TCP is supposed to retain the same krtt values for sending the next
packet in the queue. However, IOS TCP backs off yet again, causing a slightly slower sending of
packets in the retransmission queue. The impact of this is supposed to be minimal. Once the packets
in the retransmit queue are cleared (ACKed), TCP will return to its old state of sending data up to
the window advertised by the peer.
Workaround: There is no workaround.
Resolved Caveats—Cisco IOS Release 12.2(24a)
All of the Catalyst 5000 RSM/VIP2 images have been deferred in Cisco IOS Release 12.2(24a). The
software solution is Cisco IOS Release 12.2(24b). See the caveats listed under “Resolved
Caveats—Cisco IOS Release 12.2(24b).”
software solution is Cisco IOS Release 12.2(24b). See the caveats listed under “Resolved
Caveats—Cisco IOS Release 12.2(24b).”