Specifications

1414
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S
TCP/IP Host-Mode Services
• CSCeb07106
Symptoms: The following error message appears in the log of a Cisco router:
%TCP-6-TOOBIG: Tty0, too many bytes of options (44)
Conditions: This symptom is observed when numerous TCP options are configured on the router.
Workaround: Reduce the number of TCP options used (for example, selective-ack, timestamps, or
BGP md5-password).
Wide-Area Networking
• CSCdx72556
Symptoms Link-control-protocol (LCP) negotiations may fail, and a “failed to negotiate with peer”
message may be displayed.
Conditions This symptom is observed on a Cisco universal access server if the peer sends more than
five Configure-Negative acknowledgments (CONFNAKs) or Configure-Rejects (CONFREJs) on
the link for the current or previous LCP negotiation.
Workaround Configure the ppp max-failure 10 command on the link to allow the remote peer to
exhaust the Negative acknowledgment (NAK) or Reject acknowledgment (REJ) count and resume
negotiations before the Cisco universal access server drops the link.
• CSCeb33417
Symptoms: A router may reload when it tries to add a permanent virtual circuit (PVC) to a bundle
link.
Conditions: This symptom is observed when a normal Local Management Interface (LMI) frame is
received without the User-Network Interface (UNI) fragmentation header. This causes the frame to
be processed on the bundle link instead of on the bundle.
Workaround: There is no workaround.
• CSCec08632
Symptoms: If a ping to the tunnel end of an L2TP network server (LNS) fails, a large number of
packets are continuously generated, and the router may reload with a memory allocation failure error
message.
Conditions: This symptom is observed on a Cisco router that is configured for voluntary Layer 2
Tunneling Protocol (L2TP) or client-initiated L2TP tunneling.
Workaround: There is no workaround.
• CSCec13050
Symptoms: A router may reload when you enter the show running-config privileged EXEC
command after a channel group interface is created on the router.
Conditions: This symptom is observed if you create the channel group interface, configure Frame
Relay (FR) encapsulation on the interface, and then delete the interface without first removing the
FR encapsulation.
Workaround: Remove the FR encapsulation before deleting the channel group interface.
• CSCin51321
Symptoms: Traffic that is switched via Frame Relay may not pass through a 2-port multichannel T3
port adapter (PA-MC-2T3+) in unchannelized mode.