cc/td/doc/product/software/ios112
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for the 1600 Series for Cisco IOS Release 11.2P

Release Notes for the 1600 Series for Cisco IOS Release 11.2P

January 12, 1998

These release notes describe the new features and significant software components for Cisco IOS Release 11.2 P up to and including Release 11.2(11) P for Cisco 1600 series routers.

Introduction

These release notes discuss the following topics:

Cisco IOS Release 11.2 Paradigm

Similar to a train rolling down a track and picking up passengers, after a release of Cisco IOS software is released to customers it picks up software fixes along the way and is rereleased as maintenance releases. Maintenance releases provide the most stable software for your network, for the features you need. In addition to the mainline software "train," there is an early deployment (ED) train. The ED train-Release 11.2 P-delivers fixes to software defects and support for new Cisco platforms and features. Figure 1 shows the Cisco IOS 11.2 and 11.2 P train software releases.


Figure 1:

Cisco IOS Release 11.2 Software Releases
Note Cisco 1600 series routers run only Release 11.2 P software.

Release 11.2 P includes all the functionality of the features described in Table 1 and Table 2 in the section "Cisco IOS Feature Sets for Cisco 1600 Series Routers", all the features described in the section "Additional Software Features for the Cisco 1600 series", and the software caveat information for Release 11.2.

To determine which Cisco IOS maintenance release is running on your Cisco 1600 series router, log on to the router and enter the show version User EXEC command, as shown below:

router> show version
Cisco Internetwork Operating System Software 
IOS (tm) 1600 Software (C1600-Y-L), Version 11.2(8.5)P, MAINTENANCE INTERIM SOFTWARE
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Fri 12-Sep-97 00:36 by ccai
Image text-base: 0x0200544C, data-base: 0x023028C0
ROM: System Bootstrap, Version 11.1(10)AA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
ROM: 1600 Software (C1600-BOOT-R), Version 11.1(10)AA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) 
router uptime is 1 minute
System restarted by reload
System image file is "master/c1600-y-l.112-8.5.P", booted via tftp from 223.255.254.254
cisco 1601 (68360) processor (revision C) with 9728K/512K bytes of memory.
Processor board ID 05681524, with hardware revision 00000000
Bridging software.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
1 Ethernet/IEEE 802.3 interface(s)
1  serial(sync/async) network interface(s)
System/IO memory with parity disabled
2048K bytes of DRAM onboard 8192K bytes of DRAM on SIMM 
System running from RAM
8K bytes of non-volatile configuration memory.
8192K bytes of processor board PCMCIA flash (Read/Write)
Configuration register is 0x0

Cisco 1600 Series Routers

The Cisco 1600 series routers deliver the next-generation set of features and benefits for small-office Internet and intranet access: WAN flexibility, end-to-end security, end-to-end quality of service, ease of use, deployment, and management. The Cisco 1600 series routers connect small offices with Ethernet LANs to the public Internet and to a company's internal intranet or corporate LAN through several WAN connections such as ISDN, asynchronous serial, and synchronous serial. The Cisco 1600 series routers include the following models: Cisco 1601, Cisco 1602, Cisco 1603, Cisco 1604, and Cisco 1605-R.

Cisco 1601 through Cisco  1604 router models include one Ethernet port, one built-in WAN port, and one WAN interface card expansion slot for additional connectivity and flexibility. The Cisco 1601 includes a built-in serial WAN port; the Cisco 1602 has an onboard 56-kbps four-wire channel service unit/data service unit (CSU/DSU); the Cisco 1603 has an ISDN BRI S/T port; and the Cisco 1604 includes an ISDN BRI U interface with a built-in NT1 device. The Cisco 1605-R has two Ethernet LAN interfaces and one WAN interface card slot.

The following WAN interface cards are supported by the Cisco 1600 series routers:

Cisco IOS Documentation

For Cisco IOS Release 11.2, the Cisco IOS documentation set consists of eight documentation modules. Each documentation module has a configuration guide, a command reference, and five supporting documents.

Note The most up-to-date Cisco IOS documentation can be found on the latest Documentation CD-ROM and on the Web. These electronic documents contain updates and modifications made after the paper documents were printed.

The books and chapter topics are as follows:

Books Chapter Topics
· Configuration Fundamentals Configuration Guide

· Configuration Fundamentals Command Reference

 Access Server and Router Product Overview

User Interface

System Images and Configuration Files

Using ClickStart, AutoInstall, and Setup

Interfaces

System Management

· Security Configuration Guide

· Security Command Reference

 Network Access Security

Terminal Access Security

Accounting and Billing

Traffic Filters

Controlling Router Access

Network Data Encryption with Router Authentication

· Access Services Configuration Guide

· Access Services Command Reference

 Terminal Lines and Modem Support

Network Connections

AppleTalk Remote Access

SLIP and PPP

XRemote

LAT

Telnet

TN3270

Protocol Translation

Configuring Modem Support and Chat Scripts

X.3 PAD

Regular Expressions

· Wide-Area Networking Configuration Guide

· Wide-Area Networking Command Reference

 ATM

Dial-on-Demand Routing (DDR)

Frame Relay

ISDN

LANE

PPP for Wide-Area Networking

SMDS

X.25 and LAPB

· Network Protocols Configuration Guide, Part 1

· Network Protocols Command Reference, Part 1

 IP

IP Routing

· Network Protocols Configuration Guide, Part 2

· Network Protocols Command Reference, Part 2

 AppleTalk

Novell IPX

· Network Protocols Configuration Guide, Part 3

· Network Protocols Command Reference, Part 3

 Apollo Domain

Banyan VINES

DECnet

ISO CLNS

XNS

· Bridging and IBM Networking Configuration Guide

· Bridging and IBM Networking Command Reference

 Transparent Bridging

Source-Route Bridging

Remote Source-Route Bridging

DLSw+

STUN and BSTUN

LLC2 and SDLC

IBM Network Media Translation

DSPU and SNA Service Point Support

SNA Frame Relay Access Support

APPN

NCIA Client/Server Topologies

IBM Channel Attach

· Cisco IOS Software Command Summary

· Access Services Quick Configuration Guide

· System Error Messages

· Debug Command Reference

· Cisco Management Information Base (MIB) User Quick Reference

These documents are available as printed manuals or electronic documents. For electronic documentation of Release 11.2 router and access server software features, refer to the Cisco IOS Release 11.2 configuration guides and command references located in the Cisco IOS Release 11.2 database on the Documentation CD-ROM. You can also access Cisco technical documentation on the World Wide Web at http://www.cisco.com.

New Features in Release 11.2(11) P for the Cisco 1600 Series Routers

This section describes the new Cisco IOS Firewall feature set and Context-Based Access Control feature, available only in software release 11.2(11) P and above.

The Cisco IOS Firewall Feature Set: Context-Based Access Control

The Cisco IOS Firewall feature set combines existing Cisco IOS firewall technology and the new context-based access control feature to provide an effective, robust firewall.

The Cisco IOS Firewall feature set is designed to prevent unauthorized, external individuals from gaining access to your internal network, and to block attacks on your network, while at the same time allowing authorized users to access network resources.

You can use the Cisco IOS Firewall feature set to configure your Cisco IOS device as:

The Ciso IOS Firewall feature set provides the following capabilities:

Context-based access control (CBAC) is a new feature which provides intelligent filtering of packets through the firewall. CBAC creates temporary openings in the firewall to permit packets that are part of a permissible session. (These packets are normally blocked at the firewall.) A permissible session is one that originates from within your protected internal network.

New Features in Release 11.2(10) P for the Cisco 1600 Series Routers

Cisco IOS software Release 11.2(10) P and above supports the following features in Cisco 1600 router plus feature sets:

Virtual Private Dial-up Networks

Virtual private dial-up networks (VPDN) allow separate and autonomous protocol domains to share common access infrastructure including modems, access servers, and ISDN routers. VPDN uses the Level 2 Forwarding protocol (L2F) which permits the tunneling of link level frames.

Using L2F tunneling, an Internet Service Provider (ISP) or other access service can create a virtual tunnel to link a customer's remote sites or remote users with corporate home networks. In particular, a network access server at the ISP point of presence (POP) exchanges PPP messages with the remote users, and communicates by L2F requests and responses with the customer's home gateway to set up tunnels. L2F passes protocol-level packets through the virtual tunnel between endpoints of a point-to-point connection.

Frames from the remote users are accepted by the ISP POP, stripped of any linked framing or transparency bytes, encapsulated in L2F, and forwarded over the appropriate tunnel. The customer's home gateway accepts these L2F frames, strips the L2F encapsulation, and process the incoming frames for the appropriate interface.

Note This implementation of VPDN supports PPP dial-up only.

To configure virtual private dial-up networks, see the "PPP for Wide-Area Networking" section of the Wide-Area Networking Configuration Guide. This information is also available at the following URL on the Documentation CD-ROM and on CCO (as described in the section "Cisco Connection Online" later in this document):

http://www.cisco.com/univercd/data/doc/software/11_2/cwan/4cppp.htm#INDEX11038

RADIUS

Remote Authentication Dial-In User Service (RADIUS) is a distributed client/server system that secures networks against unauthorized access. In the Cisco implementation, RADIUS clients run on Cisco routers and send authentication requests to a central RADIUS server, which contains all user authentication and network service access information. RADIUS is a fully open protocol, distributed in source code format, that can be modified to work with any security system currently available on the market.

Cisco supports RADIUS under its Authentication, Authorization, and Accounting (AAA) security paradigm. RADIUS can be used with other AAA security protocols, such as TACACS+, Kerberos, or local username lookup. RADIUS has been implemented in a variety of network environments that require high levels of security while maintaining network access for remote users.

Use RADIUS in the following network environments that require access security:

RADIUS is not suitable in the following network security situations:

To configure RADIUS on a Cisco 1600 router, see the "Configuring Network Access Security" section of the Security Configuration Guide. This information is also available at the following URL on the Documentation CD-ROM and on CCO (as described in the section "Cisco Connection Online" later in this document):

http://www.cisco.com/univercd/data/doc/software/11_2/csecur/2caaa.htm

New Features in Release 11.2(9) P for the Cisco 1600 Series Routers

This section provides information about the new Cisco 1600 hardware introduced with Cisco IOS software Release 11.2(9) P:

New Features in Release 11.2 P for the Cisco 1600 Series Routers

This section is divided into the following subjects:

Routing Protocols

This section describes routing protocol features that are new in the initial release of Cisco IOS Release 11.2 P.

IP Protocol and Feature Enhancements

The following new IP protocol software features are available:

A stub router is the peripheral router in a hub-and-spoke network topology. Stub routers commonly have a WAN connection to the hub router and a small number of LAN network segments (stub networks) that are connected directly to the stub router. To provide full connectivity, the hub routers can be statically configured to know that a particular stub network is reachable via a specified access router. However, if there are multiple hub routers, many stub networks, or asynchronous connections between hubs and spokes, the overhead required to statically configure knowledge of the stub networks on the hub routers becomes too great.
ODR simplifies installation of IP stub networks in which the hub routers dynamically maintain routes to the stub networks. This is accomplished without requiring the configuration of an IP routing protocol at the stub routers. With ODR, the stub advertises IP prefixes corresponding to the IP networks that are configured on its directly connected interfaces. Because ODR advertises IP prefixes, rather than IP network numbers, ODR is able to carry Variable Length Subnet Mask (VLSM) information.
Once ODR is enabled on a hub router, the router begins installing stub network routes in the IP forwarding table. The hub router can also be configured to redistribute these routes into any configured dynamic IP routing protocols. IP does not need to be configured on the stub router. With ODR, a router is automatically considered to be a stub when no IP routing protocols have been configured on it.
The routing protocol that ODR generates is propagated between routers using Cisco Discovery Protocol (CDP). Thus, ODR is partially controlled by the configuration of CDP. Specifically,

  • If CDP is disabled, the propagation of ODR routing information will cease.

  • By default, CDP sends updates every 60 seconds. This update interval may not be frequent enough to provide fast reconvergence of IP routers on the hub router side of the network. A faster reconvergence rate may be necessary if the stub connects to several hub routers via asynchronous interfaces (such as modem lines).

  • ODR may not work well with dial-on-demand routing (DDR) interfaces, as CDP packets will not cause a DDR connection to be made.

It is recommended that IP filtering be used to limit the network prefixes that the hub router will permit to be learned dynamically through ODR. If the interface has multiple logical IP networks configured (via the IP secondary command), only the primary IP network is advertised through ODR.
Open Shortest Path First (OSPF) Enhancements

The following features have been added to Cisco's OSPF software:

The feature allows the consolidation on a single routing protocol and the benefits of the OSPF routing protocol across the entire network, without incurring excess connection costs.
If the router is part of a point-to-point topology, only one end of the demand circuit needs to be configured for OSPF On-Demand Circuit operation. In point-to-multipoint topologies, all appropriate routers must be configured with OSPF On-Demand Circuit. All routers in an area must support this feature--that is, be running Cisco IOS Software Release 11.2 or greater.
OSPF Not-So-Stubby-Areas (NSSA) defines a more flexible, hybrid method, whereby stub areas can import external OSPF routes in a limited fashion, so that OSPF can be extended across the stub to backbone connection.
NSSA enables OSPF to be extended across a stub area to backbone area connection to become logically part of the same network.

Network Address Translation

Network Address Translation (NAT) provides a mechanism for a privately addressed network to access registered networks, such as the Internet, without requiring a registered subnet address. This eliminates the need for host renumbering and allows the same IP address range to be used in multiple intranets.

With NAT, the privately addressed network (designated as "inside") continues to use its existing private or obsolete addresses. These addresses are converted into legal addresses before packets are forwarded onto the registered network (designated as "outside"). The translation function is compatible with standard routing; the feature is required only on the router connecting the inside network to the outside domain.

Translations can be static or dynamic in nature. A static address translation establishes a one-to-one mapping between the inside network and the outside domain. Dynamic address translations are defined by describing the local addresses to be translated and the pool of addresses from which to allocate outside addresses. Allocation is done in numeric order and multiple pools of contiguous address blocks can be defined.

NAT:

Because the addressing scheme on the inside network may conflict with registered addresses already assigned within the Internet, NAT can support a separate address pool for overlapping networks and translate as appropriate.

Applications that use raw IP addresses as a part of their protocol exchanges are incompatible with NAT. Typically, these are less common applications that do not use fully qualified domain names.

Multimedia and Quality of Service

The following features have been added to Cisco's multimedia and quality of service software:

RSVP requires both a network implementation and a client implementation. Applications need to be RSVP-enabled to take advantage of RSVP functionality. Currently, Precept provides an implementation of RSVP for Windows-based PCs. Companies such as Sun and Silicon Graphics have demonstrated RSVP on their platforms. Several application developers are planning to take advantage of RSVP in their applications.
RED is enabled on a per-interface basis. It "throttles back" lower-priority traffic first, allowing higher-priority traffic (as designated by an RSVP reservation or the IP precedence value) to continue unabated.
RED works with RSVP to maintain end-to-end quality of service during peak traffic loads. Congestion is avoided by selectively dropping traffic during peak load periods. This is performed in a manner designed to damp out waves of sessions going through TCP slow start.
Existing networks can be upgraded to better handle RSVP and priority traffic. Additionally, RED can be used in existing networks to manage congestion more effectively on higher-speed links where fair queuing is expensive.
Exercise caution when enabling RED on interfaces that support multiprotocol traffic (in addition to TCP/IP), such as IPX or AppleTalk. RED is not designed for use with these protocols and could have deleterious affects.
RED is a queuing technique; it cannot be used on the same interface as other queuing techniques, such as Standard Queuing, Custom Queuing, Priority Queuing, or Fair Queuing.
Topologies that have high-speed links feeding into lower-speed links--such as a central site to a remote or branch sites--often experience bottlenecks at the remote end because of the speed mismatch. Generic Traffic Shaping helps eliminate the bottleneck situation by throttling back traffic volume at the source end.
Routers can be configured to transmit at a lower bit rate than the interface bit rate. Service providers or large enterprises can use the feature to partition, for example, T1 or T3 links into smaller channels to match service ordered by customers.
Generic Traffic Shaping implements a Weighted Fair Queuing (WFQ) on an interface or subinterface to allow the desired level of traffic flow. The feature consumes router memory and CPU resources, so it must be used judiciously to regulate critical traffic flows while not degrading overall router performance.

Multiprotocol Routing

The following enhancement has been made to Cisco's multiprotocol routing:

These enhancements are particularly applicable in networking environments having many low-speed links (typically in hub-and-spoke topologies); in Non-Broadcast-Multiple-Access (NBMA) wide-area networks such as Frame Relay, ATM, or X.25 backbones; and in highly redundant, dense router-router peering configurations. It should be noted that the basic Enhanced IGRP routing algorithm that exhibits very fast convergence and guaranteed loop-free paths has not changed, so there are no backwards compatibility issues with earlier versions of Cisco IOS software.

Switching Features

The following feature has been added to Cisco's switching software:

The ability to route and bridge the same protocol on multiple independent sets of interfaces of the same Cisco IOS software-based router makes it possible to route between these routed and the bridged domains within that router. IRB provides a scalable mechanism for integration of Layer 2 and Layer 3 domains within the same device.
Integrated routing and bridging provides:

  • Scalable, efficient integration of Layer 2 and Layer 3 domains: The IRB functionality allows you to extend the bridge domains or VLANs across routers while maintaining the ability to interconnect them to the routed domains through the same router.

  • Layer 3 address conservation: You can extend the bridge domains and the VLAN environments across the routers to conserve the Layer 3 address space and still use the same router to interconnect the VLANs and bridged domains to the routed domain.

  • Flexible network reconfiguration: Network administrators gain the flexibility of being able to extend the bridge domain across the router's interfaces to provide temporary solution for moves, adds, and changes. This can be useful during migration from a bridged environment to a routed environment, or when making address changes on a scheduled basis.

Note that:

  • Currently, IRB supports three protocols: IP, IPX, and AppleTalk, in both fast switching and process switching modes.

  • IRB is not supported on ciscoBus bus platforms (the AGS+ and Cisco 7000 series).

  • IRB is supported for transparent bridging, but not for source-route bridging.

  • IRB is supported on all media-type interfaces except X.25 and ISDN bridged interfaces.

  • IRB and concurrent routing and bridging (CRB) cannot operate at the same time.

Desktop Protocols

This section describes the desktop protocol features that are new in the initial release of Cisco IOS Release 11.2.

AppleTalk Features

The following feature has been added to Cisco's AppleTalk software:

AppleTalk load balancing can reduce network costs by allowing more efficient use of network resources. Network reliability is improved because the chance that network paths between nodes will become overloaded is reduced. For convenience, load balancing is provided for networks using native AppleTalk routing protocols such as Routing Table Maintenance Protocol (RTMP) and Enhanced IGRP. AppleTalk load balancing operates with process and fast switching.

Novell Features

The following features have been added to Cisco's Novell software:

This feature allows logging of:

  • Source and destination addresses

  • Source and destination socket numbers

  • Protocol (or packet) type (for example, IPX, SPX, or NCP)

  • Action taken (permit/deny)

Matching packets and logging-enabled ACLs are sent at the process level. Router logging facilities use the IP protocol.
Protocol types supported include RIP, SAP, NCP, and NetBIOS. Supported socket types include Novell Diagnostics Packet Enhanced IGRP, and NLSP.
Plain English IPX Access Lists greatly reduce the complexity and increase the readability of IPX extended access control lists, reducing network management expense by making it easier to build and analyze the access control mechanisms used in IPX networks.

Wide-Area Networking Features

This section describes the wide-area networking features that are new in the initial release of Cisco IOS Release 11.2:

ISDN/DDR Enhancements

Dialer profile extends the flexibility of current dial-up configurations. For example, on a single ISDN PRI or PRI rotary group it is now possible to allocate separate profiles for different classes of user. These profiles may define normal DDR usage or backup usage.
Each dialer profile uses an Interface Descriptor Block (IDB) distinct from the IDB of the physical interface used to place or receive calls. When a call is established, both IDBs are bound together so that traffic can flow. As a result, dialer profiles use more IDBs than normal DDR.
This initial release of dialer profiles does not support Frame Relay, X.25, or LAPB encapsulation on DDR links or Snapshot Routing capabilities.

Frame Relay Enhancements

The following features have been added to Cisco's Frame Relay software:

Frame Relay SVCs offer cost savings via usage-based pricing instead of fixed pricing for a PVC connection, dynamic modification of network topologies with any-to-any connectivity, dynamic network bandwidth allocation or bandwidth-on-demand for large data transfers such as FTP traffic, backup for PVC backbones, and conservation of resources in private networks.
To use Frame Relay SVCs, Frame Relay SVC must be supported by the Frame Relay switches used in the network. Also, a Physical Local Loop Connection, such as a leased or dedicated line, must exist between the router (DTE) and the local Frame Relay switch.
The Frame Relay protocol defines several parameters that are useful for managing network traffic congestion. These include Committed Information Rate (CIR), Forward/Backward Explicit Congestion Notification (FECN/BECN), and Discard Eligibility (DE) bit. Cisco already provides support for FECN for DECnet and OSI, BECN for SNA traffic using direct LLC2 encapsulation via RFC 1490, and DE bit support. The Frame Relay Traffic Shaping feature builds upon this support by providing the following three capabilities:

  • Rate Enforcement on a per virtual circuit (VC) basis: A peak rate can be configured to limit outbound traffic to either the CIR or some other defined value such as the Excess Information Rate (EIR).

  • Generalized BECN support on a per VC basis: The router can monitor BECNs and throttle traffic based upon BECN marked packet feedback from the Frame Relay network.

  • Priority/Custom/First In, First Out Queuing (PQ/CQ/FIFO) support at the VC level: This allows for finer granularity in the prioritization and queuing of traffic, providing more control over the traffic flow on an individual VC.

Frame Relay Traffic Shaping:

  • Eliminates bottlenecks in Frame Relay network topologies with high-speed connections at the central site, and low-speed connections at the branch sites. Rate Enforcement can be used to limit the rate at which data is sent on the VC at the central site.

  • Provides a mechanism for sharing media by multiple VCs. Rate Enforcement allows the transmission speed used by the router to be controlled by criteria other than line speed, such as the CIR or EIR. The Rate Enforcement feature can also be used to pre-allocate bandwidth to each VC, creating a Virtual Time Division Multiplexing network.

  • Dynamically throttles traffic, based on information contained in BECN-tagged packets received from the network. With BECN based throttling, packets are held in the router's buffers to reduce the data flow from the router into the Frame Relay network. The throttling is done on a per VC basis and the transmission rate is adjusted based on the number of BECN-tagged packets received.

  • Defines queuing at the VC or subinterface level. Custom Queuing with the Per VC Queuing and Rate Enforcement capabilities enable Frame Relay VCs to be configured to carry multiple traffic types (such as IP, SNA and IPX), with bandwidth guaranteed for each traffic type.

The three capabilities of the Traffic Shaping for Frame Relay feature require the router to buffer packets to control traffic flow and compute data rate tables. Because of this router memory and CPU utilization, these features must be used judiciously to regulate critical traffic flows while not degrading overall Frame Relay performance.

IBM Functionality

This section describes the IBM network software features and support that are new in the Cisco IOS Release 11.2(8) P.

New Features

The following new IBM software features are available:

The NCIA Server supports SNA and NetBIOS sessions over a variety of LAN and WAN connections, including dial-up connections. The NCIA architecture supports clients with full SNA stacks--providing all advanced SNA capabilities, unlike some split-stack solutions.
NCIA Server enhancements provide:

  • Simplified client configuration: It is no longer necessary to predefine ring numbers, and the NCIA Server supports optional dynamic assignment of MAC addresses. There is no Logical Link Control, type 2 (LLC2), at the client. The client is configured as an end station, not a router peer.

  • Scalability: The limit is based on the number of LLC connections in the central site router rather than RSRB peer connections.

Note that each client is a full SNA PU with one or more LUs. As such, each device requires one LLC connection at the central site router.
RTR enables the following functions to be performed:

  • Troubleshoot problems by checking the time delays between devices (such as a router and a MVS host) and the time delays on the path from the source device to the destination device at the protocol level.

  • Send SNMP traps and/or SNA Alerts/Resolutions when one of the following has occurred: a user-configured threshold is exceeded, a connection is lost and reestablished, or a timeout occurs and clears. Thresholds can also be used to trigger additional collection of time delay statistics.

  • Perform pre-problem analysis by scheduling the RTR and collecting the results as history and accumulated statistics. The statistics can be used to model and predict future network topologies.

The RTR feature is currently available only with feature sets that include IBM support. A CiscoWorks Blue network management application will be available to support the RTR feature. Both the CiscoWorks Blue network management application and the router use the Cisco Round Trip Time Monitor (RTTMON) MIB. This MIB is also available with Release 11.2.

Data Link Switching+ (DLSw+) Features and Enhancements

The following features have been added to Cisco's DLSw+ software. These features had previously been available with Remote Source-Route Bridging (RSRB). To provide these features for DLSw+, the Cisco IOS software uses a component known as Virtual Data Link Control (VDLC) that allows one software component to use another software component as a data link.

With this feature, LNM can be used to manage Token Ring LANs, Control Access Units (CAUs), and Token Ring attached devices over a DLSw+ network. All management functions continue to operate as they would in an RSRB network or source-route bridged network.
With this feature, NSP can be configured in remote routers, and DLSw+ can provide the path for the remote service point PU to communicate with NetView. This allows full management visibility of resources from a NetView 390 console, while concurrently offering the value-added features of DLSw+ in an SNA network.
DSPU concentration consolidates the appearance of up to 255 physical units into a single PU appearance to VTAM, minimizing memory and cycles in central site resources (VTAM, NCP, and routers) and speeding network startup. Used in conjunction with DLSw+, network availability and scalability can be maximized.

Security Features

This section describes the security features that are new in the initial release of Cisco IOS Release 11.2.

New Features

This feature can be used to build multiprotocol Virtual Private Networks (VPNs), using encrypted Generic Routing Encapsulation (GRE) tunnels. It can also be used to deploy secure telecommuting services, Intranet privacy, and virtual collaborative or community-of-interest networks.
All components of this feature are subject to International Traffic in Arms Regulations (ITAR) export restrictions. Encryption is currently IP only, though it does support multiprotocol GRE tunnels. This feature is most appropriately deployed in a relatively small number of routers, with a logically flat or star-shaped encryption topology. Load-sharing of the encryption/decryption function is not supported. Without a Certification Authority (CA), the one-time authentication effort increases exponentially with the number of routers. Router authentication requires the network administrator to compare the hashes produced by the routers. This version of encryption is not IPSEC compliant.

TACACS+ Enhancements

The following features have been added to Cisco's TACACS+ software:

Single Connection is an optimization whereby the network access server maintains a single TCP connection to one or more TACACS+ daemons. The connection is maintained in an open state for as long as possible, instead of being opened and closed each time a session is negotiated. It is expected that Single Connection will yield performance improvements on a suitably constructed daemon.
Currently, only the CiscoSecure daemon V1.0.1 supports Single Connection. The network access server must be explicitly configured to support a Single Connection daemon. Configuring Single Connection for a daemon that does not support this feature will generate errors when TACACS+ is used.
The network access server can support both SENDAUTH and SENDPASS simultaneously. It detects if the daemon is able to support SENDAUTH and, if not, will use SENDPASS instead. This negotiation is virtually transparent to the user, with the exception that the down-rev daemon may log the initial SENDAUTH packet as unrecognized.
SENDAUTH functionality requires support from the daemon, as well as the network access server.

Network Management

This section describes the network management features that are new in the initial release of Cisco IOS Release 11.2.

MIBs Supported

The following MIB support has been added:

See the "New Features" subsection in the "IBM Functionality" section for details.

Cisco IOS Feature Sets for Cisco 1600 Series Routers

This section lists Cisco IOS software feature sets available in Cisco IOS Release 11.2 P.
These features are available in specific features sets on specific platforms.

Table 1 and Table 2 use these feature set matrix symbols to identify features:

Feature Set
Matrix Symbol 		Description
Basic This feature is offered in the basic feature set.
-- This feature is not offered in the feature set.
Plus This feature is offered in the Plus feature set, not in the basic feature set.
Encrypt This feature is offered in the encryption feature sets, which consist of 40-bit (Plus 40) or 56-bit (Plus 56) data encryption feature sets.

Cisco IOS images with 40-bit Data Encryption Standard (DES) support may legally be distributed to any party eligible to receive Cisco IOS software. The 40-bit DES is not a cryptographically strong solution and should not be used to protect sensitive data.

Cisco IOS images with 56-bit DES are subject to International Traffic in Arms Regulations (ITAR) controls and have a limited distribution. Images to be installed outside the U.S. require an export license. Customer orders may be denied or subject to delay because of United States government regulations. Contact your sales representative or distributor for more information, or send e-mail to export@cisco.com.

Table 1 and table 2 list the standard feature sets supported in Release 11.2 P.


Table 1: Feature Set Matrix for Cisco 1600 Series Routers
Standard Feature Sets Options
IP

Basic, Plus, Encrypt

IP/IPX

Basic, Plus, Encrypt

IP/AppleTalk

Basic, Plus, Encrypt

IP/IPX/AppleTalk

Basic, Plus, Encrypt

IP/IPX/IBM

Basic, Plus, Encrypt

Firewall1

Basic

IP/Firewall1

Basic

IP/IPX/Firewall Plus1

Plus

IP/IPX/AT/IBM/Firewall Plus 561

Encrypt


1 Available only in Release 11.2(11)P and later releases.

Feature Set Tables

The Cisco IOS software is available in different feature sets depending on the platform. Table 2 lists the feature sets for the Cisco 1600 series routers.


Table 2: Cisco 1600 Series Routers Feature Sets
Feature Sets
Features Contained in
Feature Sets 		IP IP/IPX IP/
AppleTalk 		IP/IPX/
AppleTalk 		IP/IPX/
IBM 		Firewall1
 LAN Support

--

AppleTalk 1 and 22

--

--

Basic

Basic

--

--

Integrated routing and bridging (IRB)3

Basic

Basic

Basic

Basic

Basic

--

IP

Basic

Basic

Basic

Basic

Basic

--

Novell IPX4

--

Basic

--

Basic

Basic

--

Transparent bridging

Basic

Basic

Basic

Basic

Basic

--

 WAN Services

--

Asynchronous

Basic

Basic

Basic

Basic

Basic

--

Frame Relay

Basic

Basic

Basic

Basic

Basic

--

Frame Relay SVC support (DTE)

Plus

Plus

Plus

Plus

Plus

--

Frame Relay traffic shaping

Basic

Basic

Basic

Basic

Basic

--

HDLC

Basic

Basic

Basic

Basic

Basic

--

ISDN 5

Basic

Basic

Basic

Basic

Basic

--

PPP6

Basic

Basic

Basic

Basic

Basic

--

SMDS

Basic

Basic

Basic

Basic

Basic

--

Switched 56

Basic

Basic

Basic

Basic

Basic

--

X.25

Basic

Basic

Basic

Basic

Basic

--

SLIP asynchronous only

Basic

Basic

Basic

Basic

Basic

--

 WAN Optimization

--

Bandwidth-on-demand7

Basic

Basic

Basic

Basic

Basic

--

Custom and priority queuing

Basic

Basic

Basic

Basic

Basic

--

Dial backup

Basic

Basic

Basic

Basic

Basic

--

Dial-on-demand

Basic

Basic

Basic

Basic

Basic

--

Header, link, and payload compression

Basic

Basic

Basic

Basic

Basic

--

Header and link compression

Basic

Basic

Basic

Basic

Basic

--

Snapshot routing

Basic

Basic

Basic

Basic

Basic

--

Weighted fair queuing

Basic

Basic

Basic

Basic

Basic

--

IPX and SPX spoofing

--

Basic

--

Basic

Basic

--

 IP Routing

--

AppleTalk SMRP Multicast

--

--

Plus

Plus

--

--

Enhanced IGRP

Basic

Basic

Basic

Basic

Basic

--

IGRP

Basic

Basic

Basic

Basic

Basic

--

IP Multicast (PIM)

Plus

Plus

Plus

Plus

Plus

--

Network Address Translation (NAT)

Plus

Plus

Plus

Plus

Plus

--

On Demand Routing (ODR)

Basic

Basic

Basic

Basic

Basic

--

OSPF

Plus

Plus

Plus

Plus

Plus

--

OSPF On Demand Circuit (RFC 1793)

Plus

Plus

Plus

Plus

Plus

--

PIM

Plus

Plus

Plus

Plus

Plus

--

RIP

Basic

Basic

Basic

Basic

Basic

--

RIP Version 2

Basic

Basic

Basic

Basic

Basic

--

 Other Routing

--

IPX RIP

--

Basic

--

Basic

Basic

--

RTMP

--

--

Basic

Basic

--

--

NLSP

--

Plus

--

Plus

Plus

--

 Multimedia and Quality of  Service

--

Generic traffic shaping

Plus

Plus

Plus

Plus

Plus

--

Random Early Detection (RED)

Plus

Plus

Plus

Plus

Plus

--

Resource Reservation Protocol (RSVP)

Plus

Plus

Plus

Plus

Plus

--

 Management

--

SNMP

Basic

Basic

Basic

Basic

Basic

--

Telnet

Basic

Basic

Basic

Basic

Basic

--

Console port

Basic

Basic

Basic

Basic

Basic

--

Networking Timing Protocol (NTP)

Plus

Plus

Plus

Plus

Plus

--

Simple Networking Timing Protocol (SNTP)

Basic

Basic

Basic

Basic

Basic

--

 Security

--

Access lists

Basic

Basic

Basic

Basic

Basic

--

Cisco IOS Firewall: Context-Based Access Control

--

--

--

--

--

Encrypt

Extended access lists

Basic

Basic

Basic

Basic

Basic

--

TACACS Plus

Basic

Basic

Basic

Basic

Basic

--

RADIUS

Plus

Plus

Plus

Plus

Plus

--

GRE tunneling

Basic

Basic

Basic

Basic

Basic

--

Lock and key

Basic

Basic

Basic

Basic

Basic

--

Network layer encryption, 40-bit (Plus 40) and 56-bit (Plus 56)

 Encrypt

 Encrypt

 Encrypt

 Encrypt

 Encrypt

--

Virtual Private Dialup Network

Plus

Plus

Plus

Plus

Plus

--


1 Includes Firewall, IP/Firewall, IP/IPX/Firewall Plus, and IP/IPX/AT/IBM/Firewall Plus 56 feature sets. Available only in Cisco IOS Release 11.2(11)P and later releases.
2 AppleTalk load balancing is available in Cisco IOS Release 11.2.
3 IRB supports IP, IPX, and AppleTalk; it is supported for transparent bridging, but not for SRB; it is supported on all media-type interfaces except X.25 and ISDN bridged interfaces; and IRB and concurrent routing and bridging (CRB) cannot operate at the same time.
4 In Cisco IOS Release 11.2, the Novell IPX feature includes Display SAP by Name, IPX Access Control List violation logging, and plain-English IPX access lists.
5 ISDN support includes calling line identification (CLI/ANI), ISDN subaddressing, and applicable WAN optimization features.
6 PPP includes support for LAN protocols supported by the feature set, address negotiation, PAP and CHAP authentication, and PPP compression. Multilink PPP is included with Cisco IOS Release 11.0(4) and later releases.
7 Bandwidth-on-demand means two B-channel calls to the same destination.

Upgrading to a New Software Release

If you are upgrading to Cisco IOS Release 11.2 from an earlier Cisco IOS software release, you should save your current configuration file before configuring your access server with the Cisco IOS Release 11.2 software. An unrecoverable error could occur during download or configuration.

Cisco IOS Upgrade Procedure

For instructions on downloading a current Cisco IOS release from the CCO Trivial File Transfer Protocol (TFTP) server, go to the following URL. This URL is subject to change without notice.

http://www.cisco.com/kobayashi/sw-center

The Software Center window is displayed.

Step 1 Click Cisco IOS Software. The Cisco IOS Software window is displayed.

Step 2 Click Cisco IOS 11.2. The Cisco 11.2 Software Upgrade Planner window is displayed.

Step 3 Click Download Cisco IOS 11.2 Software. The Software Checklist window is displayed.

Step 4 Select the appropriate information in each section of the Software Checklist window.

Step 5 Click Execute. The software release is downloaded to your desktop computer.

Step 6 Transfer the software release to a local TFTP server on your network, using a terminal emulation application, such as TCP Connect.

Step 7 Log on to your router. Copy the software release from your TFTP server to your router, using the copy tftp command.

Memory Requirements

Table 3 describes the memory requirements for the Cisco 1600 series platform's feature set supported by Cisco IOS Release 11.2 P.


Table  3: Cisco 1600 Series--Memory Requirements
Cisco IOS Rel 11.2(10) P
Feature Set 		Required Memory for
Cisco 1601--1604
(Run From Flash) 		Required Memory for
Cisco 1605-R
(Run From RAM)
Flash1 DRAM Flash1 DRAM
IP Only 4 MB2 2 MB2 2 MB2 8 MB2
IP Plus 6 MB 4 MB 4 MB 8 MB
IP Plus 40 6 MB 4 MB 4 MB 8 MB
IP Plus 56 6 MB 4 MB 4 MB 8 MB
IP/IPX 4 MB 2 MB 2 MB 8 MB
IP/IPX Plus 6 MB 4 MB 4 MB 8 MB
IP/IPX Plus 40 6 MB 4 MB 4 MB 10 MB
IP/IPX Plus 56 6 MB 4 MB 4 MB 10 MB
IP/Appletalk 4 MB 2 MB 2 MB 8 MB
IP/Appletalk Plus 6 MB 4 MB 4 MB 8 MB
IP/Appletalk Plus 40 6 MB 4 MB 4 MB 10 MB
IP/Appletalk Plus 56 6 MB 4 MB 4 MB 10 MB
IP/IPX/Appletalk 6 MB 4 MB 4 MB 8 MB
IP/IPX/Appletalk Plus 6 MB 4 MB 4 MB 10 MB
IP/IPX/Appletalk Plus 40 6 MB 4 MB 4 MB 10 MB
IP/IPX/Appletalk Plus 56 6 MB 4 MB 4 MB 10 MB
IP/IPX/IBM 6 MB 4 MB 4 MB 10 MB
IP/IPX IBM Plus 8 MB 4 MB 4 MB 12 MB
IP/IPX IBM Plus 40 8 MB 4 MB 4 MB 12 MB
IP/IPX IBM Plus 56 8 MB 4 MB 4 MB 12 MB

1 When a system is running from Flash memory, you cannot update the system while it is running. You must use the Flash load helper.
2 This is the default memory size.

Caveats for Release 11.2(1) Through 11.2(11) P

This section describes possibly unexpected behavior by Release 11.2(11) P. Unless otherwise noted, these caveats apply to Release 11.2 up to and including 11.2(11) P. The caveats listed here describe only the serious problems. For the complete list of caveats against Release 11.2, use the Documentation CD-ROM or access CCO as described in the section "Cisco Connection Online" later in this document.

Access Server

The workaround at this time is to reload the router. Issuing the shut and no shut commands on the affected interface does not help. [CSCdj41613]

AppleTalk

To work around this problem, do one of the following:
- Remove autoselect and use ARAP dedicated.
- Use the ARAP 2.0.1 client.
- Turn on MNP10 on the ARAP 2.1 client.
- Modify the client CCL script to extend the pause to 3 seconds before exiting. [CSCdj09817]

Basic System Services

- The router is resolving host names via an external DNS server.
- The TACACS server is down.
- The user gains access to the router via the backup "enable" method.
- The user attempts to Telnet from the router to a host on the network.
After the Telnet is initiated, the router immediately reloads.
The workaround for this problem is to not configure the ip identd command or to disable the identd process with the global command no ip identd (which is the default). [CSCdj19961]
An error was introduced by CSCdj42505 in Release 11.2 P and CSCdj22736 in Release 11.1CC. It does not exist in other IOS releases. [CSCdj44667]
Instead it exposed a bug in older implementations of the developers kit TACACS+ daemon (freeware) and will cause certain command authorizations to fail.
All freeware daemon versions prior to version 3.0.13 are subject to this problem including the ACE Safeword Security Server daemon. CiscoSecure daemons are not affected. [CSCdj66657]
To use the single line option, specify username*password in the username field and the word "arap" (lower case) in the password field.
The ARA 2.1 client returns the error "The connection attempt has failed. The server you called is not a valid Remote Access."
The ARA 3.0 client returns the error "User authentication failed. Check your user name and password and try again." [CSCdj68015]

EXEC and Configuration Parser

IBM Connectivity

%Must remove the remote-peer to change the lf
The workaround is to use TCP encapsulation. [CSCdi55075]
The workaround is to turn off the focal point feature in the AS400. See the network attribute configuration panel in the AS/400. [CSCdi67820]
The problem is related to the way DLSw backup peers are configured. This problem occurs only if the local router is configured with backup peer commands and the remote router also has a configured peer and is not promiscuous.
The workaround is to remove the DLSw backup peer configuration. [CSCdj21664]
The output of the show fras command showed ls-reset backup enabled. In order to reconnect the PUs, the fras backup rsrb statement must be removed or the serial interfaces configuration deleted and then readded. [CSCdj39306]
To work around this problem, configure a MAC address on the target device that is always the same whether it is canonical or non-canonical (for example, 4242.6666.ffff). [CSCdj48606]
> System was restarted by bus error at PC 0x6C75DC[_Mfree(0x6c75b6)+0x26], address 0xFFFFFFF8[_etext(0x73ab50)+0xff8c54a8]
> Image text-base: 0x00012000[__start(0x12000)+0x0], data-base: 0x0073AB50[__etext(0x73ab50)+0x0]
> FP: 0x872C74[_etext(0x73ab50)+0x138124], RA: 0x6588BC[_session_failure_clean_up(0x658502)+0x3ba]
> FP: 0x872EB8[_etext(0x73ab50)+0x138368], RA: 0x65C6E6[_process_cp_status_sig(0x65c2da)+0x40c]
> FP: 0x8730F0[_etext(0x73ab50)+0x1385a0], RA: 0x64D820[_xxxmss00(0x64d64e)+0x1d2]
> FP: 0x873210[_etext(0x73ab50)+0x1386c0], RA: 0xB720C[_process_hari_kari(0xb720c)+0x0]
[CSCdj51051]
The problem typically occurs when NetBIOS is utilized to allow workstations to communicate between Ethernet and Token Ring. It also occurs when SNA is used.
The workaround is to disable fast-switching by using the no source-bridge transparent fastswitch command or configuring the end stations to use frames with a payload of less than or equal to 1500 bytes. [CSCdj62385]
[abort(0x601f2c3c)+0x8]
[crashdump(0x601f0b20)+0x94]
[process_handle_watchdog(0x601c2f08)+0xb4]
[signal_receive(0x601b7d58)+0xa8]
[process_forced_here(0x60169424)+0x68]
[locate_node_index(0x607dbcc0)+0x64]
[etext(0x60849e00)+0xcbee04]
[CSCdj67966]
System was restarted by bus error at PC 0xCC6B8, address 0xFC4AFC82 4000 Software (C4000-JS-M), Version 11.2(10.3), MAINTENANCE INTERIM SOFTWARE Compiled Mon 01-Dec-97 19:45 by ckralik (current version) Image text-base: 0x00012000, data-base: 0x0076AE64
The workaround is to use TCP encapsulation for RSRB or to switch to DLSw. [CSCdj68261]

Interfaces and Bridging

A workaround for this problem is to execute the clear line command on all V.110 lines after the following events:

  • Power up initialization.

  • Using the modem hold-reset command on all 12 ports.

[CSCdj23972]
This problem has minimal impact on the performance of the multidrop line because a FEP usually resorts to individual polling. [CSCdj33392]
Data corruption is possible if you are using Rev2 Mueslix and an release earlier than Release 11.2(9)P. [CSCdj43672]
Mixed Microcom/Mica configurations cannot be supported with this bug present. A similar crash with the same stack trace was also seen with only Microcom modems, but this is much harder to reproduce. [CSCdj44456]

IP Routing Protocols

A workaround is to configure a loopback on the interface whose address is greater than any other address on the router. [CSCdj37962]
snmpset: The value given has incorrect type or length. [CSCdj43710]
%SYS-3-CPUHOG: Task ran for 2608 msec (73/65), Process = BGP scanner, PC = 176388
[CSCdj45966]

ISO CLNS

LAT

LLC Type 2

Miscellaneous

RSP software based encryption does not work when encrypted traffic is flowing over any Cisco 7500 VIP interface. Customers with VIP2-40 or higher interfaces need to run VIP distributed encryption. There is no workaround for other VIP2 models other than using an older non-VIP interface. [CSCdi74884]
HSRP routers send hello packets from a virtual MAC address, which is a function of the standby group number. When the ring heals, both routers are active and sourcing hellos from the same (virtual) MAC address.
FDDI devices must strip their frames off the ring. One method of doing this is to recognize frames by source MAC address. When the problem occurs, the FDDI PAs will mistakenly strip the other router's packets from the FDDI ring without processing them. This causes both routers to remain active since they do not hear hellos from their neighbors.
This problem can also occur when FDDI PAs are used in conjunction with other FDDI interfaces, such as the FIP or Cisco 4000 series FDDI module.
If only one standby group is in use, the standby use-bia command can be used on both routers to cause hellos to be sourced from the burned in address instead of the virtual MAC address. This will prevent the problem.
If the problem occurs, performing an interface reset by issuing the shut and no shut commands returns the routers to a normal state.
Increasing the HSRP hello intervals causes the problem to occur less often since the routers will be able to tolerate a longer period of instability before missing enough hellos to go active. [CSCdj30049]

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

Wide-Area Networking

See associated caveat CSCdi52882. [CSCdi52067]
%AIP-3-AIPREJCMD: Interface ATM5/0, AIP driver rejected Setup VC command (error code 0x0008)
%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=1500, VPI=10, VCI=257) on Interface ATM5/0, (Cause of the failure: Failed to have the driver to accept the VC)
The limit to the number of VPI values used depends on the configuration of the vc-per-vp configuration parameter. When vc-per-vp is 1024 (the default), 33 VPI values can be used. To work around this limitation, implement the atm vc-per-vp command on the particular ATM interface, which lowers the number of VCs per VP. This results in a corresponding increase in the number of VPI values that can be used. [CSCdi67839]
A workaround is to disconnect and reconnect every BRI interface once the router is fully operational.
This problem seems to be related to CSCdj04241. [CSCdj04625]
During normal behavior, the point-to-point subinterface should go down when the primary DLCI fails. If a secondary DLCI fails, the subinterface stays up, but traffic destined for that DLCI only will fail. [CSCdj11056]
As a workaround, configure the no dialer hold-queue command. [CSCdj12397]
%SYS-2-LINKED: Bad enqueue of 8F3288 in queue 9570C8
-Process= "LAPF Input", ipl= 6, pid= 36
-Traceback= EBE30 EAA88 4A73B4 4A8E10
[CSCdj29721]
To work around this problem, turn off ATM traffic-shaping over that interface. Another workaround is to use Cisco IOS Release 11.2(2) or earlier, including Release 11.1. [CSCdj45778]
The workaround is to remove the ip tcp header-compression or ppp multilink commands. [CSCdj53093]
atm_parse_packet(ATM2/0):Invalid VC(0) received, type=A2D2
atm_parse_packet(ATM2/0):Invalid VC(0) received, type=A2D2
atm_parse_packet(ATM2/0):Invalid VC(0) received, type=A2D2
In addition, the input errors displayed by the show interface atm command increase.
This problem seems to occur only with Release 11.2(6). The workaround is to downgrade to Release 11.2(4) [CSCdj57704]
There is no workaround, for this intermittent problem. [CSCdj62139]

Caveats for Release 11.2(1) Through 11.2(10)

This section describes possibly unexpected behavior by Release 11.2(10) P. Unless otherwise noted, these caveats apply to Release 11.2 up to and including 11.2(10) P. The caveats listed here describe only the serious problems. For the complete list of caveats against Release 11.2, use the Documentation CD-ROM or access CCO as described in the section "Cisco Connection Online" later in this document.

Access Server

AppleTalk

Basic System Services

%RSP-3-RESTART: interface Serial12/0/0:28, output stuck
The problem occurs on Cisco routers in the 7000 family using the CT3 or 4/8 port FSIP cards or any serial interface under Cisco IOS Release 11.1(10)CA, 11.1(11), and 11.2. It has been observed only under oversubscribed traffic load.
As a workaround, configure the interface for FIFO queueing via the no fair-queue command.
The command transmit-buffers backing-store is on by default when an interface is configured for weighted fair-queueing. If the no fair-queue interface command is used, which changes the queueing strategy to FIFO, then transmit-buffers backing-store is off by default.
This caveat has been resolved in the following Cisco IOS releases: 11.2(6.2)P 11.1(11.4) 11.1(11)CA 11.1(11.4)IA [CSCdj12815]
This problem has been seen only with Cisco IOS Release 11.2 or later. [CSCdj36356]
For example, a problem was found with a Cisco 7500 using a large number of Fast Ethernet and/or Ethernet interfaces and one or more FDDI interfaces. The pool of packet memory should have allocated 80 percent of the memory to the Ethernet and Fast Ethernet interfaces, which use an MTU of 1536. Instead it received 20 percent of the memory, and the lone FDDI interface with MTU 4512 got 80 percent of the packet memory.
The problem occurred with 55 Ethernet, 6 Fast Ethernet, and 1 FDDI network interfaces. The problem did not occur with fewer interfaces, specifically 36 Ethernet, 5 Fast Ethernet, and 1 FDDI interfaces.
The problem may show up as a high number of input drops on some router interfaces. [CSCdj55428]
The following are known workarounds:
- Increase the input queue to 175. ([75]Original Queue amount+[100] per exception dump x.x.x.x command)
- Remove the exception dump x.x.x.x command.
[CSCdj58035]
The workaround is to remove and then reenable frame-relay traffic-shaping to clear its counters. [CSCdj65742]

IBM Connectivity

System was restarted by bus error at PC 0x8B5902, address 0x4AFC4AFC PC: process_snmp_trs_tg_inc
0x8B5CAC:_process_ms_data_req_trs(0x8b5aaa)+0x202 0x87E5FE:_xxxtos00(0x87d6b0)+0xf4e 0x180E5C:_process_hari_kari(0x180e5c)+0x0
[CSCdj36824]
This state may occur if the downstream LU has previously failed to reply to ACTLU, or if the host has failed to respond to a NOTIFY (available or not available) from DSPU within a timeout period of 20 seconds.
Recovery requires the host operator to recycle the LU at the host. [CSCdj45783]
The workaround is to not reconfigure virtual rings or remote peers while executing a show source command. [CSCdj49973]
interface TokenRing0/0
ip address
multiring ip
source-bridge proxy-explorer
Note the absence of the source-bridge locRn bn remRn command.
The source-bridge proxy-explorer statement does not show up in the configuration unless the SRB triplet is configured.
A workaround for this problem is to configure the no source-bridge proxy-explorer command. [CSCdj51631]

Interfaces and Bridging

If this incoherency occurs and does not cause a router crash, it may instead cause cbus switching to be automatically disabled, and the interface resorts to fast switching (or SSE switching if SSE switching were also configured). [CSCdi43526]
Symptoms include the following message being displayed to the console:
%CBUS-3-CATMREJCMD: ATM0/0 Teardown VC command failed (error code 0x0008)
Saving the RSM configuration and reloading its image will clear the error condition. [CSCdj41802]

IP Routing Protocols

The router can be forced to install the matching route by using the clear ip route * command. [CSCdj32471]
"System restarted by error - an arithmetic exception, PC 0x60286234"
The program counter value points to an EIGRP IOS routine. [CSCdj38361]
This problem exists in all releases starting with Release 10.3. This will be fixed in 11.1 and newer releases. [CSCdj53804]
When the serial interface is used for incoming packets and the ATM interface for outgoing packets, there is no problem. Incoming packets on the ATM interface and outgoing packets on the serial interface also experience this problem.
We used several Cisco IOS releases, with always the same effect. It seems that incoming packets are not fast switched. [CSCdj59076]
The workaround is to redistribute the connected network into OSPF to retain connectivity to those networks. [CSCdj60959]

ISO CLNS

LLC Type 2

There is no workaround. [CSCdj62026]

Miscellaneous

Novell IPX, XNS, and Apollo Domain

As a workaround, try one of the following:

  • Issue the shut and no shut commands on the affected interface.

  • Reconfigure the IPX network using the no ipx network command, followed by ipx network. [CSCdj53721]

Symptoms could be loss of network connectivity or a slow memory leak until the router cannot allocate any more memory. You need to reload the router to correct this situation. [CSCdj57257]

Wide-Area Networking

The workaround is to set the timeout values the same using the lmi-t392dce parameter. [CSCdj53354]
There is no known workaround. [CSCdj57498]

Caveats for Release 11.2(1) Through 11.2(9)

This section describes possibly unexpected behavior by Release 11.2(9) P. Unless otherwise noted, these caveats apply to Release 11.2 up to and including 11.2(9) P. The caveats listed here describe only the serious problems. For the complete list of caveats against Release 11.2, use the Documentation CD-ROM or access CCO as described in the section "Cisco Connection Online" later in this document.

Basic System Services

The workaround for copying from flash to TFTP or RCP is to use the following command instead of a flash keyword: 
copy flash:rcp | tftp}
This does not work with bootflash however. [CSCdj38964]
%SYS-6-STACKLOW: Stack for level CXBus Interfaces running low, 0/1000
The router might halt after displaying this message. [CSCdi54119]
APPN-DLUR-MIB
IBM-6611-APPN-MIB
CISCO-CIPCSNA-MIB
CISCO-CIPLAN-MIB
CISCO-CIPTCPIP-MIB
CISCO-SNA-LLC-MIB
SNA-NAU-MIB
CISCO-TN3270SERVER-MIB
OLD-CISCO-IP-MIB
BGP4-MIB
LAN-EMULATION-CLIENT-MIB
RFC1406-MIB
RMON-MIB
IF-MIB
RFC1398-MIB
OLD-CISCO-INTERFACES-MIB
CISCO-PING-MIB
CISCO-QLLC01-MIB [CSCdj34766]
snmp-server view no-flash internet included
snmp-server view no-flash ciscoFlashMIB excluded
snmp-server community public view no-flash ro
The result is the SNMP polls using the public community string can access objects in the entire MIB space (internet) except for those objects in the ciscoFlashMIB space. This affects any NMS applications that rely on the ciscoFlashMIB objects. [CSCdj35443]

IBM Connectivity

%APPN-6-APPNSENDMSG: Ended DLUR connection with DLUS NETA.SJMVS1
%APPN-7-MSALERT: Alert LU62004 issued with sense code 0x8A00008 by XXXSMPUN
%APPN-6-APPNSENDMSG: Starting DLUR connection with DLUS NETA.SJMVS4
%APPN-7-APPNETERROR: CP_STATUS FSM: Unanticipated CP_STATUS message received
Each subsequent broadcast locate received by the router causes the following messages to be displayed and about 1920 bytes of APPN memory to be leaked:
%APPN-7-APPNETERROR: MAP_INPUT_SET_TO_ROW: invalid input value=0x80200080
%APPN-7-APPNETERROR: State Error lcb: 60C05CC0 pcid: DA839C70FB1548CB row: 22 col: 0
This problem occurs when two links are active to the same node and the CP-CP sessions are split between these two links and the link with contention loser is stopped. To clear this problem, stop and restart the APPN subsystem. If the CP-CP sessions are between the router and the host, you can also clear this problem by terminating either CP-CP session on the host. [CSCdj33718]
System was restarted by bus error at PC 0x3784864, address 0xF0110208 PC 0x3784864[_Qfind_front(0x3040a04+0x743e44)+0x1c] RA: 0x36C1F2E[_queue_find_front(0x3040a04+0x68151c)+0xe] RA: 0x36CC554[_psbmfrm(0x3040a04+0x68bb30)+0x20] RA: 0x36CDAF6[_psp00(0x3040a04+0x68cfd4)+0x11e] RA: 0x314BD78[_process_hari_kari(0x3040a04+0x10b374)+0x0] [CSCdj44198]
%LNMC-3-BADCLSIRET: bogus Invalid ret code (0x7007) init_clsi_op_proc, bogus -Traceback= 60791120 6078FE48 6078FDC4 607890E0 6078ED48 60226648 60226634 [CSCdj45268]

Interfaces and Bridging

IP Routing Protocols

LAT

%LAT-3-BADDATA: Tty124, Data pointer does not correspond to current packet
When many LAT sessions are active, and a received data slot starts in the last 14 bytes of a full Ethernet frame, data for that slot is discarded. [CSCdi82343]

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

VINES

Wide-Area Networking

%SYS-3-INVMEMINT: Invalid memory action (free) at interrupt level
[CSCdj42341]

The show x25 vc command will cause the router to unexpectedly restart if there is a combination of locally switched virtual circuits and other virtual circuits. [CSCdj50405]

Caveats for Release 11.2(1) Through 11.2(8)

This section describes possibly unexpected behavior by Release 11.2(8). Unless otherwise noted, these caveats apply to Release 11.2 up to and including 11.2(8). The caveats listed here describe only the serious problems. For the complete list of caveats against Release 11.2, use the Documentation CD-ROM or access CCO as described in the section "Cisco Connection Online" later in this document.

Access Server

AppleTalk

Basic System Services

There is no workaround on the router side. On the DNS server side, configuring DNS TTL to be one minute or longer might work around this problem. However, this workaround might not be acceptable for some applications. [CSCdj16824]
% Non-volatile configuration memory has not been set up
The user's script is used to change passwords. Current testing indicates that it might be a software checksum error. [CSCdj18107]
To run type A7, A6, or AA boot Flash devices and use images prior to this bug fix, format boot Flash with an image containing this bug fix. Then load an older image onto the newly formatted boot Flash SIMM. [CSCdj20681]
%RSP-2-QAERROR: reused or zero link error, write at addr 00C0 (QA) log 2600C040, data 00070000 00000000
This message might be followed by the following error and a crash:
Unexpected exception, CPU signal 10, PC = 0x601C4658
This message is caused by a memory access problem in the diagnostic code handling the original QA error. [CSCdj29751]
The ciscoFlashMIB can essentially be disabled (SNMP is prevented from polling this MIB) via use of SNMP views. For example, the SNMP configuration snmp-server community public ro can be changed to the following:
snmp-server view no-flash internet included
snmp-server view no-flash ciscoFlashMIB excluded
snmp-server community public view no-flash ro
The result is the SNMP polls using the public community string can access objects in the entire MIB space (internet) except for those objects in the ciscoFlashMIB space. This affects any NMS applications that rely on the ciscoFlashMIB objects. [CSCdj35443]

EXEC and Configuration Parser

IBM Connectivity

An APPN image might restart because of a CPU HOG problem when processing a link failure event by the Directory Service APPN process (xxxdns00). This might occur when a lot of locate requests are pending. There is no known workaround. The router is forced to restart by the system watchdog process (software-forced reload event). [CSCdj26423]
Because other network events (link outages, and so forth) can trigger a node to send a TDU, this problem might not appear after a 60-day uptime--it might occur much later or not at all. However, any APPN router running in the network for over 60 days is at risk of experiencing this problem.
Stopping and restarting APPN is a workaround for this problem until the next timer wrap, which can be up to 45 days, but might be less depending on the current value of the timer. Reloading the router will reset the timer and avoid the problem for an additional 60 days. [CSCdj29014]
If the downstream device never responds to the outstanding bind, the DLUR router will wait indefinitely and not free the local-form session ID (lfsid). This might cause a situation in which the host tries to reuse an lfsid after it has sent an unbind request, but the DLUR rejects the new bind request because it believes that this lfsid is in use. If the host continuously tries to use the lfsid that the DLUR believes is in use, no new sessions can be established. This problem occurs only when the downstream device does not respond to a bind request. [CSCdj30386]
%APPN-6-APPNSENDMSG: Ended DLUR connection with DLUS NETA.SJMVS1
%APPN-7-MSALERT: Alert LU62004 issued with sense code 0x8A00008 by XXXSMPUN
%APPN-6-APPNSENDMSG: Starting DLUR connection with DLUS NETA.SJMVS4
%APPN-7-APPNETERROR: CP_STATUS FSM: Unanticipated CP_STATUS message received
Each subsequent broadcast locate received by the router causes the following messages to be displayed and about 1920 bytes of APPN memory to be leaked:
%APPN-7-APPNETERROR: MAP_INPUT_SET_TO_ROW: invalid input value=0x80200080
%APPN-7-APPNETERROR: State Error lcb: 60C05CC0 pcid: DA839C70FB1548CB row: 22 col: 0
This problem occurs when two links are active to the same node and the CP-CP sessions are split between these two links and the link with contention loser is stopped. The APPN subsystem should be stopped and restarted to clear this problem. If the CP-CP sessions are between the router and the host, terminating either CP-CP session on the host will also clear this problem. [CSCdj33718]

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

LAT

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

TN3270

VINES

Wide-Area Networking

Current PC: 0x90F61C[bcopy(0x90f56c)+0xb0] FP: 0xCC65C4[_etext(0x96f3ec)+0x3571d8] RA: 0x5E1EF2[_fr_svc_send_msg_to_nli(0x5e1eca)+0x28] FP: 0xCC65E8[_etext(0x96f3ec)+0x3571fc] RA: 0x5DD98C[_FRU0_Setup(0x5dd8e2)+0xaa] FP: 0xCC6620[_etext(0x96f3ec)+0x357234] RA: 0x5DD894[_svc_process_l3_event(0x5dd786)+0x10e] FP: 0xCC6664[_etext(0x96f3ec)+0x357278] RA: 0x5DA17A[_l3_ie_parse(0x5d9d32)+0x448] FP: 0xCC66A4[_etext(0x96f3ec)+0x3572b8] RA: 0x5D9B84[_l3_ie_parse_process(0x5d9b14)+0x70] FP: 0xCC66C0[_etext(0x96f3ec)+0x3572d4] RA: 0x1CC372[_process_hari_kari(0x1cc372)+0x0]
Current PC: 0x5E1D8E[_fr_svc_call_id_to_nli(0x5e1cf0)+0x9e] FP: 0xCC5CCC[_etext(0x970900)+0x3553cc] RA: 0x5E2176[_fr_svc_send_msg_to_nli(0x5e214e)+0x28] FP: 0xCC5CF0[_etext(0x970900)+0x3553f0] RA: 0x5DDC10[_FRU0_Setup(0x5ddb66)+0xaa] FP: 0xCC5D28[_etext(0x970900)+0x355428] RA: 0x5DDB18[_svc_process_l3_event(0x5dda0a)+0x10e] FP: 0xCC5D6C[_etext(0x970900)+0x35546c] RA: 0x5DA3FE[_l3_ie_parse(0x5d9fb6)+0x448] FP: 0xCC5DAC[_etext(0x970900)+0x3554ac] RA: 0x5D9E08[_l3_ie_parse_process(0x5d9d98)+0x70] FP: 0xCC5DC8[_etext(0x970900)+0x3554c8] RA: 0x1CC3BA[_process_hari_kari(0x1cc3ba)+0x0] [CSCdj13019]
Upon bootup, OIR, microcode reload, and cbus complex restarts, the router shows CCBTIMEOUT error messages on VIPs that result in a disabled wedged status. This problem occurs with bad PAs and PAs in a "not-ready" state. The cause of the problem is when PCI access is tried and the PA does not respond, thus resulting in CCBTIMEOUTS. [CSCdj21639]

Caveats for Release 11.2(1) Through 11.2(4)

This section describes possibly unexpected behavior by Release 11.2(4). Unless otherwise noted, these caveats apply to Release 11.2 up to and including 11.2(4). The caveats listed here describe only the serious problems. For the complete list of caveats against Release 11.2, use the Documentation CD-ROM or access CCO as described in the section "Cisco Connection Online" later in this document.

Basic System Services

%SNMP-3-CPUHOG: Processing Get of lifEntry.75.34
[CSCdi93084]

Interfaces and Bridging

If the table has the entries with indices of:
0000.0000.0001 0000.0000.0002 0000.0000.0003 0000.0000.0005
a getnext of 0000.0000.0002 returns the index 0000.0000.0005 because 0000.0000.0003 is the index requested + 1
a getnext of 0000.0000.0003 returns the index 0000.0000.0005 because 0000.0000.0005 is greater than the requested index + 1. [CSCdi84559]

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

A workaround is to turn off TCP header compression. [CSCdj01681]

Wide-Area Networking

EXEC and Configuration Parser

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.