Cisco Cisco IOS Software Release 12.0 S Release Notes
1957
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(23)S3
Basic System Services
•
CSCdy74705
Symptoms: A memory corruption may occur on a Network Processing Engine 200 (NPE-200).
Conditions: This symptom is observed on the NPE-200 of a Cisco 7200 series router. This symptom
is observed when a high amount of traffic is present on the router and when there are packet sizes
that are greater than 1524 bytes in size. The occurrence of this symptom may be related to port
adapter arrangements.
is observed when a high amount of traffic is present on the router and when there are packet sizes
that are greater than 1524 bytes in size. The occurrence of this symptom may be related to port
adapter arrangements.
Workaround: Rearrange the port adapters or upgrade to Cisco IOS Release 12.0(24)S or a later
release.
release.
•
CSCea22886
Symptoms: When an entry in the ciscoPingTable MIB variable is set to be valid, high memory
utilization may occur gradually because memory is not released by the “dead*” process of a Simple
Network Management Protocol (SNMP) ping.
utilization may occur gradually because memory is not released by the “dead*” process of a Simple
Network Management Protocol (SNMP) ping.
Conditions: This symptom is observed on a Cisco 12000 series after the router has been upgraded
from an earlier Cisco IOS release to Cisco IOS Release 12.2(23)S.
from an earlier Cisco IOS release to Cisco IOS Release 12.2(23)S.
Workaround: Exclude the ciscoPingTable MIB variable from the configuration by entering the
snmp-server view view name ciscoPingTable excluded global configuration command.
snmp-server view view name ciscoPingTable excluded global configuration command.
•
CSCea36491
Symptoms: When a Telnet session is made to a router after a VTY session pauses indefinitely, the
user in the Telnet session may not be able to enter the configuration mode. When these symptoms
occur, interfaces may enter the wedged state with Simple Network Management Protocol (SNMP)
traffic.
user in the Telnet session may not be able to enter the configuration mode. When these symptoms
occur, interfaces may enter the wedged state with Simple Network Management Protocol (SNMP)
traffic.
Conditions: This behavior is observed on ATM and Packet over SONET (POS) interfaces. This
behavior is not platform-specific.
behavior is not platform-specific.
Workaround: Disable Simple Network Management Protocol (SNMP) configuration traps by
entering the no snmp-server enable traps config global configuration command.
entering the no snmp-server enable traps config global configuration command.
•
CSCeb08027
Symptoms: The snmp mib target list global configuration command is not displayed when the
show running-config EXEC command is entered on the secondary Performance Routing Engine
(PRE). However, the snmp mib target list global configuration command is displayed when the
show startup-config EXEC command is entered on the PRE.
show running-config EXEC command is entered on the secondary Performance Routing Engine
(PRE). However, the snmp mib target list global configuration command is displayed when the
show startup-config EXEC command is entered on the PRE.
Conditions: This symptom is observed on the PRE of a Cisco 10000 series.
Workaround: There is no workaround.
IP Routing Protocols
•
CSCdu53656
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a
Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by
default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the
malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject
a malformed packet. BGP MD5 is a valid workaround for this problem.
Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by
default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the
malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject
a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, see the advisory
at
at
.