Specifications

1121
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S2
Conditions: This symptom is observed when the no ipv6 pim command is entered on some
subinterfaces of a physical Ethernet interface and when PIM is enabled on several subinterfaces of
the same physical Ethernet interface. The symptom affects both IPv4 and IPv6, and configurations
with multicast and OSPF Hello messages.
Workaround: There is no workaround.
• CSCee04316
Symptoms: A TN-2-BADCONN message may appear in the log and may be quickly followed by an
FIB Disable message, indicating that distributed CEF is disabled on all VIPs. The IPC buffers usage
may grows very large (up to 600 MB) and these buffers may not be reclaimed.
Conditions: This symptom is observed on a distributed Cisco platform that uses IPC communication
with a central route processor and distributed cards when commands are executed on the card (for
example, the execute-on command, the show controller vip command, or other commands) and
when the Telnet connection is lost before the execution of the command has completed.
Workaround: Reload the router to restore normal operation. Review operational monitoring
processes and avoid scripts that collect information from the cards.
• CSCee87891
Symptoms: SNMP entries may be deleted when you configure SNMP or when you reload the router
on which SNMP is configured.
Conditions: This symptom is observed when an SNMP user is configured with the same name or
host name as a community.
Workaround: There is no workaround.
• CSCee95282
Symptoms: A router may generate a very large remote processing time report that may take between
10 and 25 seconds to be generated.
Conditions: This symptom is observed when you enter the rtr responder command for the first time
and you do not reload the router.
Workaround: Reload the router after you have entered the rtr responder command.
• CSCef46191
Symptoms: A specifically crafted Transmission Control Protocol (TCP) connection to a telnet or
reverse telnet port of a Cisco device running Internetwork Operating System (IOS) may block
further telnet, reverse telnet, Remote Shell (RSH), Secure Shell (SSH), and in some cases Hypertext
Transport Protocol (HTTP) access to the Cisco device. Telnet, reverse telnet, RSH and SSH sessions
established prior to exploitation are not affected.
All other device services will operate normally.
Conditions: User initiated specially crafted TCP connection to a telnet or reverse telnet port results
in blocking further telnet sessions. Whereas, services such as packet forwarding, routing protocols
and all other communication to and through the device remains unaffected.
Workaround: The detail advisory is available at
http://www.cisco.com/warp/public/707/cisco-sa-20040827-telnet.shtml.